Internal service access via followed HTTP redirects
Published Dec 20, 2023 · Updated Aug 2, 2024
Server-side request forgery in MLflow before 2.9.2 allows remote attackers to access internal HTTP services through the tracking server. The _get_http_response_with_retries helper passes attacker-influenced URLs to requests.Session.request while allowing redirects by default without restricting redirect destinations. No authentication or user interaction is required; exposed internal services or cloud metadata can be read, and obtained cloud credentials can enable command execution.
Summary
What happened
Server-side request forgery in MLflow before 2.9.2 allows remote attackers to access internal HTTP services through the tracking server. The _get_http_response_with_retries helper passes attacker-influenced URLs to requests.Session.request while allowing redirects by default without restricting redirect destinations. No authentication or user interaction is required; exposed internal services or cloud metadata can be read, and obtained cloud credentials can enable command execution.
The record
- CVE
- CVE-2023-6974
- Published
- Dec 20, 2023
- Updated
- Aug 2, 2024
- Vendor
- MLflow Project
- Product
- MLflow
- Classifications
- CWE-918, T1190
- Attack vector
- network
- Privileges
- unauthenticated
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?
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 SSRF proof of conceptproof of concept · demonstrated
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