Arbitrary file write via drive-relative path traversal
Published Nov 16, 2023 · Updated Aug 2, 2024
Path traversal in MLflow before 2.8.1 allows remote attackers to write arbitrary files to a Windows tracking server. The validate_path_is_safe function accepts drive-relative paths such as C:../path, which Windows path handling converts into traversal segments before the PUT write. Exploitation requires network access to the artifact upload interface and can place files outside the intended artifact directory with the server process's permissions.
Summary
What happened
Path traversal in MLflow before 2.8.1 allows remote attackers to write arbitrary files to a Windows tracking server. The validate_path_is_safe function accepts drive-relative paths such as C:../path, which Windows path handling converts into traversal segments before the PUT write. Exploitation requires network access to the artifact upload interface and can place files outside the intended artifact directory with the server process's permissions.
The record
- CVE
- CVE-2023-6015
- Published
- Nov 16, 2023
- Updated
- Aug 2, 2024
- Vendor
- MLflow Project
- Product
- MLflow
- Classifications
- CWE-22, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 16, 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 <=latest
What conditions does exploitation require?
What is affected?
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