CVE-2024-0520 json
Remote Code Execution due to Full Controlled File Write in mlflow/mlflow
published 2024-06-06 2 y ago modified 2026-09-10 59 d ago also BIT-mlflow-2024-0520 , EUVD-2024-1934 , GHSA-5q6c-ffvg-xcm9 , PYSEC-2024-239
- cvss
- 10.0
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.4%
- EPSS 2.4% chance of exploitation in 30 days, percentile 84%
- public exploits
- 0
- none known
Summary
A vulnerability in mlflow/mlflow version 8.2.1 allows for remote code execution due to improper neutralization of special elements used in an OS command ('Command Injection') within the `mlflow.data.http_dataset_source.py` module. Specifically, when loading a dataset from a source URL with an HTTP scheme, the filename extracted from the `Content-Disposition` header or the URL path is used to generate the final file path without proper sanitization. This flaw enables an attacker to control the file path fully by utilizing path traversal or absolute path techniques, such as '../../tmp/poc.txt' or '/tmp/poc.txt', leading to arbitrary file write. Exploiting this vulnerability could allow a malicious user to execute commands on the vulnerable machine, potentially gaining access to data and model information. The issue is fixed in version 2.9.0.
Patch / fix
- pypi mlflow 2.9.0
- bitnami mlflow 2.9.1
- mlflow mlflow/mlflow 2.9.0
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
2.38% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- huntr.com https://huntr.com/bounties/93e470d7-b6f0-409b-af63-49d3e2a26dbc referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 10.0 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
| GitHub | 3.0 | 10.0 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| OSV | 3.0 | 10.0 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
| OSV | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | mlflow | <2.9.0 |
2.9.0 |
| bitnami | mlflow | <2.9.1 |
2.9.1 |
Affected products
- mlflow mlflow/mlflow
Classification
References
-
github.com
/mlflow/mlflow/commit/400c226953b4568f4361bc0a0c223511652c2b9d
web, patch
-
huntr.com
/bounties/93e470d7-b6f0-409b-af63-49d3e2a26dbc
web, exploit, issue-tracking, patch, third-party-advisory, advisory, evidence, report
-
nvd.nist.gov
/vuln/detail/CVE-2024-0520
advisory, web
-
github.com
/mlflow/mlflow
package
-
github.com
/pypa/advisory-database/tree/main/vulns/mlflow/PYSEC-2024-239.yaml
web
-
github.com
/advisories/GHSA-5q6c-ffvg-xcm9
advisory
Sources
- CVE List CVE-2024-0520
- GitHub Advisory GHSA-5q6c-ffvg-xcm9
- NVD CVE-2024-0520
- OSV BIT-mlflow-2024-0520
- OSV PYSEC-2024-239
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.