Security Digest · Vulnerability record
CVE-2024-3573: mlflow vulnerable to Path Traversal
mlflow/mlflow is vulnerable to Local File Inclusion (LFI) due to improper parsing of URIs, allowing attackers to bypass checks and read arbitrary files on the system.
CVSS 9.3 Critical EPSS 0.7% · p54
Should you act?
Critical and remotely reachable
No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.
- Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
- EPSS 0.7%, percentile 54: FIRST’s model estimates a 0.7% chance of exploitation activity in the next 30 days, higher than 54% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
- Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
- Only applies if your dependency tree includes
mlflow(PyPI) < 2.10.0, fixed in 2.10.0. Check your lockfile, including transitive dependencies.
What it is
mlflow/mlflow is vulnerable to Local File Inclusion (LFI) due to improper parsing of URIs, allowing attackers to bypass checks and read arbitrary files on the system. The issue arises from the 'islocaluri' function's failure to properly handle URIs with empty or 'file' schemes, leading to the misclassification of URIs as non-local. Attackers can exploit this by crafting malicious model versions with specially crafted 'source' parameters, enabling the reading of sensitive files within at least two directory levels from the server's root.
From the GitHub advisory
mlflow/mlflow is vulnerable to Local File Inclusion (LFI) due to improper parsing of URIs, allowing attackers to bypass checks and read arbitrary files on the system. The issue arises from the 'islocaluri' function's failure to properly handle URIs with empty or 'file' schemes, leading to the misclassification of URIs as non-local. Attackers can exploit this by crafting malicious model versions with specially crafted 'source' parameters, enabling the reading of sensitive files within at least two directory levels from the server's root.
Weakness type: CWE-29.
Product: mlflow (PyPI) · Assigned by: @huntr_ai · Published: 2024-04-16
Affected and fixed versions
| Ecosystem | Package | Vulnerable | First fixed |
|---|---|---|---|
| PyPI | mlflow | < 2.10.0 | 2.10.0 |
| Vendor | Product | Affected versions (per CVE record) |
|---|---|---|
| mlflow | mlflow/mlflow | unspecified < 2.10.0 |
Severity scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| @huntr_ai | 3.0 | 9.3 Critical | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N |
| GitHub | 3.1 | 9.3 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N |
- Attack vector: network (remotely reachable)
- Attack complexity: low
- Privileges required: none (no login)
- User interaction: none
- Scope: changed (can affect other components)
CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.
Exploitation and urgency
- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation poc, automatable yes, technical impact partial.
- FIRST EPSS (model of 2026-10-21): 0.73% probability of exploitation activity in the next 30 days; percentile 54.
Timeline
- — CVE record published by @huntr_ai
- — GitHub-reviewed advisory GHSA-hq88-wg7q-gp4g published (critical)
- — CVE record last updated
Sources and references
Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.
Vulnerability records
- GitHub Advisory GHSA-hq88-wg7q-gp4g github.com
- CVE.org record CVE-2024-3573 cve.org
- NVD entry CVE-2024-3573 nvd.nist.gov
Other references from the CVE record and advisory
- huntr.com huntr.com
- github.com github.com
- github.com github.com