Arbitrary file read via unvalidated URI fragments
Published Jun 6, 2024 · Updated Aug 1, 2024
Path traversal in MLflow before 2.11.3 allows remote attackers to read arbitrary server files through crafted artifact-location URIs. The _create_experiment handler accepted artifact_location URLs containing fragments while validating only query strings, allowing traversal sequences to reach local file resolution. An unauthenticated network request to an exposed tracking server is sufficient, and access is limited to files readable by the server process.
Summary
What happened
Path traversal in MLflow before 2.11.3 allows remote attackers to read arbitrary server files through crafted artifact-location URIs. The _create_experiment handler accepted artifact_location URLs containing fragments while validating only query strings, allowing traversal sequences to reach local file resolution. An unauthenticated network request to an exposed tracking server is sufficient, and access is limited to files readable by the server process.
The record
- CVE
- CVE-2024-2928
- Published
- Jun 6, 2024
- Updated
- Aug 1, 2024
- Vendor
- MLflow Project
- Product
- MLflow
- Classifications
- CWE-22, CWE-29, T1190, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 6, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.11.3
- Affected versionversion=unspecified <2.11.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo