Client-side code execution via unescaped recipe templates
Published Feb 23, 2024 · Updated Aug 14, 2024
Cross-site scripting in MLflow 2.9.2 and earlier allows remote attackers to execute code in Jupyter via an untrusted recipe. Recipe card rendering inserts schema and stack-trace template values into HTML without Jinja escaping, allowing injected markup to execute. Execution requires a user to run and inspect an attacker-controlled recipe in Jupyter Notebook, where the injected script runs with the notebook client's privileges.
Summary
What happened
Cross-site scripting in MLflow 2.9.2 and earlier allows remote attackers to execute code in Jupyter via an untrusted recipe. Recipe card rendering inserts schema and stack-trace template values into HTML without Jinja escaping, allowing injected markup to execute. Execution requires a user to run and inspect an attacker-controlled recipe in Jupyter Notebook, where the injected script runs with the notebook client's privileges.
The record
- CVE
- CVE-2024-27132
- Published
- Feb 23, 2024
- Updated
- Aug 14, 2024
- Vendor
- MLflow Project
- Product
- MLflow
- Classifications
- CWE-79, T1204
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 23, 2024CVE publishedPublication date reported by the CVE source.
- Aug 14, 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
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