Arbitrary file read via artifact URL fragment
Published May 16, 2024 · Updated Aug 1, 2024
Path traversal in MLflow 2.9.2 through 2.12.0 allows remote attackers to read arbitrary server files through crafted artifact URLs. MLflow server handlers accepted a fragment beginning with # in artifact_location, then converted the fragment path for local filesystem access without rejecting it. An exposed tracking server with filesystem or cloud-key access is sufficient; the consequence is read-only disclosure of files available to the server process.
Summary
What happened
Path traversal in MLflow 2.9.2 through 2.12.0 allows remote attackers to read arbitrary server files through crafted artifact URLs. MLflow server handlers accepted a fragment beginning with # in artifact_location, then converted the fragment path for local filesystem access without rejecting it. An exposed tracking server with filesystem or cloud-key access is sufficient; the consequence is read-only disclosure of files available to the server process.
The record
- CVE
- CVE-2024-3848
- Published
- May 16, 2024
- Updated
- Aug 1, 2024
- Vendor
- MLflow Project
- Product
- MLflow
- Classifications
- CWE-22, CWE-29, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 16, 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=2.11.0 <2.12.1
- Affected versionversion=unspecified <2.12.1
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