Arbitrary file read via unvalidated artifact path
Published Mar 24, 2023 · Updated Feb 19, 2025
Path traversal in MLflow before 2.2.1 allows remote attackers to read arbitrary files through the artifact download endpoint. The _download_artifact handler passed validate_path_is_safe itself to the validator instead of the attacker-controlled artifact_path, leaving traversal sequences unchecked. Exposure requires mlflow server or mlflow ui with an artifact endpoint reachable without access controls, and file reads inherit the server's filesystem or remote-storage access.
Summary
What happened
Path traversal in MLflow before 2.2.1 allows remote attackers to read arbitrary files through the artifact download endpoint. The _download_artifact handler passed validate_path_is_safe itself to the validator instead of the attacker-controlled artifact_path, leaving traversal sequences unchecked. Exposure requires mlflow server or mlflow ui with an artifact endpoint reachable without access controls, and file reads inherit the server's filesystem or remote-storage access.
The record
- CVE
- CVE-2023-1177
- Published
- Mar 24, 2023
- Updated
- Feb 19, 2025
- Vendor
- MLflow Project
- Product
- MLflow
- Classifications
- CWE-29, CWE-22, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 24, 2023CVE publishedPublication date reported by the CVE source.
- Feb 19, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <2.2.1
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