Remote file access vulnerability in `mlflow server` and `mlflow ui` CLIs
GHSA-83fm-w79m-64r5 · published 2023-05-01
- Severity
- Critical
- CVSS score
- Not scored
- Chance of exploitation (EPSS)
- No CVE
- Fixed in
- 2.3.1
Users of the MLflow Open Source Project who are hosting the MLflow Model Registry using the commands using an MLflow version older than MLflow 2.3.1 may be vulnerable to a remote file access exploit if they are not limiting who can query their server (for example, by using a cloud VPC, an IP allowlist for inbound requests, or authentication / authorization middleware). This issue only affects users and integrations that run the commands. Integrations that do not make use of are unaffected; for example, the Databricks Managed MLflow product and MLflow on Azure Machine Learning do not make use of these commands and are not impacted by these vulnerabilities in any way.
Upgrade mlflow to 2.3.1 or later.
This vulnerability has been patched in MLflow 2.3.1, which was released to PyPI on April 27th, 2023. If you are using with the MLflow Model Registry, we recommend upgrading to MLflow 2.3.1 as soon as possible.
If you are using the MLflow open source commands, we strongly recommend limiting who can access your MLflow Model Registry and MLflow Tracking servers using a cloud VPC, an IP allowlist for inbound requests, authentication / authorization middleware, or another access restriction mechanism of your choosing. If you are using the MLflow open source commands, we also strongly recommend limiting the remote files to which your MLflow Model Registry and MLflow Tracking servers have access.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| mlflow | PyPI | < 2.3.1 | 2.3.1 |
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLangflow affected by Remote Code Execution via validate_code() exec()langflowExploited
- CriticalJupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routesjupyter-mcp-server
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
- CriticalMLflow: Unauthenticated full-read SSRF in webhook delivery: _validate_webhook_url bypassed via unvalidated HTTP redirects (and DNS rebindingmlflowExploited
- CriticalMLflow vulnerable to remote code execution on unauthenticated servers via third-party scorer deserialization importing caller-placed artifacmlflow
- CriticalMLflow: Environment variable injection in AI Gateway secrets enables server-side credential exfiltrationmlflow
- CriticalMLflow allows unauthorized access to multipart upload endpoints when the `--serve-artifacts` mode is enabledmlflow
- CriticalMLflow: Improper Origin Validation in MLflow Assistant /ajax-api Endpoints Enables Browser-Mediated Local Command Executionmlflow
- Criticalmlflow: FastAPI job endpoints under `/ajax-api/3.0/jobs/*` are not protected by authentication or authorizationmlflow
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.