UpTrain vulnerabilities

UpTrain version 0.7.1 and earlier creates a default user with a static username, which is also used as the default API key. The backend has an open CORS policy, allowing any website to make authenticated cross-origin requests using the default API key in the `uptrain-access-token` header. This may allow arbitrary websites to perform privileged operations on the UpTrain instance.

In UpTrain version 0.7.1 and prior, the /new_run endpoint is vulnerable to remote code execution via the checks and metadata parameters. Any user with access to UpTrain and a valid authentication method may be able to execute arbitrary code in the context of the host running UpTrain, which in most cases will be the docker container.

In UpTrain version 0.7.1 and prior, the /add_prompts endpoint is vulnerable to remote code execution via the checks and metadata parameters. Any user with access to UpTrain and a valid authentication method may be able to execute arbitrary code in the context of the host running UpTrain, which in most cases will be the docker container.

UpTrain version 0.7.1 and earlier contains a remote code execution vulnerability in the `/create_project` endpoint via the `checks` and `metadata` parameters. Any user with access to UpTrain and valid authentication can execute arbitrary code in the context of the host running UpTrain, usually a Docker container. No patch is available as of publication.