Remote file-existence disclosure via registered-model path traversal
Published Mar 24, 2023 · Updated Feb 19, 2025
Path traversal in MLflow before 2.2.2 allows remote attackers to determine whether arbitrary server-accessible files exist. The file-backed Model Registry treats an absolute registered-model name as a filesystem path, and response differences disclose whether that path exists. Exposure requires the Model Registry served by mlflow server or mlflow ui to accept unauthenticated queries; managed integrations not using those commands are unaffected.
Summary
What happened
Path traversal in MLflow before 2.2.2 allows remote attackers to determine whether arbitrary server-accessible files exist. The file-backed Model Registry treats an absolute registered-model name as a filesystem path, and response differences disclose whether that path exists. Exposure requires the Model Registry served by mlflow server or mlflow ui to accept unauthenticated queries; managed integrations not using those commands are unaffected.
The record
- CVE
- CVE-2023-1176
- Published
- Mar 24, 2023
- Updated
- Feb 19, 2025
- Vendor
- MLflow Project
- Product
- MLflow
- Classifications
- CWE-36, T1083
- 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.2
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.
Public exploit references
- huntr proof of concept for CVE-2023-1176proof 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