Arbitrary directory deletion via double-decoded paths
Published Apr 16, 2024 · Updated Aug 9, 2024
Path traversal in MLflow 2.9.2 and earlier allows remote authenticated users to delete arbitrary server directories through artifact deletion. The _delete_artifact_mlflow_artifacts handler and local_file_uri_to_path decode a supplied path twice, while delete_artifacts applies an extra unquote before directory removal. Access to artifact deletion is required; successful exploitation removes directories with the server process's filesystem permissions without disclosing file contents.
Summary
What happened
Path traversal in MLflow 2.9.2 and earlier allows remote authenticated users to delete arbitrary server directories through artifact deletion. The _delete_artifact_mlflow_artifacts handler and local_file_uri_to_path decode a supplied path twice, while delete_artifacts applies an extra unquote before directory removal. Access to artifact deletion is required; successful exploitation removes directories with the server process's filesystem permissions without disclosing file contents.
The record
- CVE
- CVE-2024-1560
- Published
- Apr 16, 2024
- Updated
- Aug 9, 2024
- Vendor
- MLflow Project
- Product
- MLflow
- Classifications
- CWE-22, T1485
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 16, 2024CVE publishedPublication date reported by the CVE source.
- Aug 9, 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.9.2
- 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
- Huntr artifact-deletion path traversal proof of conceptproof of concept · unverified
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