Unauthenticated file disclosure via unchecked artifact path
Published May 11, 2023 · Updated Jan 27, 2025
Path traversal in MLflow before 2.0.0rc0 allows remote attackers to read arbitrary server files through the /get-artifact API. The get_artifact_handler function passed the request path to the artifact repository without rejecting absolute paths, alternate separators, or parent-directory traversal sequences. No authentication or user interaction is required; disclosure is limited to files readable by the tracking-server process.
Summary
What happened
Path traversal in MLflow before 2.0.0rc0 allows remote attackers to read arbitrary server files through the /get-artifact API. The get_artifact_handler function passed the request path to the artifact repository without rejecting absolute paths, alternate separators, or parent-directory traversal sequences. No authentication or user interaction is required; disclosure is limited to files readable by the tracking-server process.
The record
- CVE
- CVE-2023-30172
- Published
- May 11, 2023
- Updated
- Jan 27, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-22, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 11, 2023CVE publishedPublication date reported by the CVE source.
- Jan 27, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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