Arbitrary code execution via MLproject entrypoint command
Published Jun 4, 2024 · Updated Aug 2, 2024
Code injection in MLflow from 1.11.0 allows remote attackers to execute arbitrary code through a crafted MLflow Project. The project runner treats the main entry-point command from MLproject YAML as executable content and launches it without filtering attacker-supplied commands. Exploitation requires a user to obtain and run the attacker's project, after which the command runs with that user's privileges on the local system.
Summary
What happened
Code injection in MLflow from 1.11.0 allows remote attackers to execute arbitrary code through a crafted MLflow Project. The project runner treats the main entry-point command from MLproject YAML as executable content and launches it without filtering attacker-supplied commands. Exploitation requires a user to obtain and run the attacker's project, after which the command runs with that user's privileges on the local system.
The record
- CVE
- CVE-2024-37061
- Published
- Jun 4, 2024
- Updated
- Aug 2, 2024
- Vendor
- MLflow Project
- Product
- MLflow
- Classifications
- CWE-20, CWE-94, T1059, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 4, 2024CVE 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=1.11.0 <=*
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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