CVE-2024-3573: lfprojects mlflow Path Traversal: '\..\filename'
Vulnerability summary
CVE-2024-3573 is a critical (CVSS 9.3) Path Traversal: '\..\filename' vulnerability in lfprojects mlflow. EPSS estimates a 0.73% chance of exploitation in the next 30 days, higher than 53.5% of scored vulnerabilities. 1 public exploit is recorded.
Timeline
- 16-04-2024PublishedVulnerability first disclosed.
- 01-08-2024Last modifiedVulnerability information updated.
Description
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 'is_local_uri' 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.
CVSS metrics
4 scores · 3 sources · 2 versions- NVDNIST9.3CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
- NVDNIST9.3CriticalCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
EPSS trend
Probability
0.73%
Chance of exploitation in the next 30 days
Percentile
54%
Versus all other CVEs
30-day change
0.00 pp
From 0.73% on 20-09-2026
Known exploited
Compare KEV catalogsNot in any of the 3 tracked catalogs.
Public exploits
1 foundExploit Reference (huntr.com)
Maturity: unknown
Weaknesses
CWE · root cause- CWE-29Path Traversal: '\..\filename'The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '\..\filename' (leading backslash dot dot) sequences that can resolve to a location that is outside of that directory.
- CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Affected systems
Lfprojects1 product
- mlflow< 2.10.0
Mlflow1 product
- mlflow/mlflow≥ unspecified, < 2.10.0
PyPI1 product
- mlflow< 438a450714a3ca06285eeea34bdc6cf79d7f6cbc | < 2.10.0
3 vendors · 3 products
References
6 links- huntr.com/bounties/8ea058a7-4ef8-4baf-9198-bc0147fc543cWEBEVIDENCEREPORTExploitIssue TrackingThird Party Advisory
- github.com/mlflow/mlflowPACKAGE