Arbitrary file write via ignored path validation
Published Dec 20, 2023 · Updated Aug 2, 2024
Unrestricted file upload in MLflow before 2.9.2 allows remote authenticated users to write arbitrary files via artifact path requests. Artifact upload handlers validate a supplied path but discard the sanitized return value, so traversal or absolute paths reach filesystem writes outside the artifact root. The issue requires access to MLflow server artifact APIs; successful requests can overwrite files with server-process privileges.
Summary
What happened
Unrestricted file upload in MLflow before 2.9.2 allows remote authenticated users to write arbitrary files via artifact path requests. Artifact upload handlers validate a supplied path but discard the sanitized return value, so traversal or absolute paths reach filesystem writes outside the artifact root. The issue requires access to MLflow server artifact APIs; successful requests can overwrite files with server-process privileges.
The record
- CVE
- CVE-2023-6976
- Published
- Dec 20, 2023
- Updated
- Aug 2, 2024
- Vendor
- MLflow Project
- Product
- MLflow
- Classifications
- CWE-434, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 20, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 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=unspecified <2.9.2
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