UI denial of service via unbounded experiment names
Published Mar 20, 2025 · Updated Mar 20, 2025
Uncontrolled resource consumption in MLflow 2.13.2 and earlier allows remote attackers to make the tracking UI unresponsive. Experiment creation and rename paths accept names containing arbitrarily many integers, while creation also accepts an unbounded artifact_location value. A network-reachable tracking server must accept a crafted experiment operation; the oversized metadata can hang UI rendering without reported data disclosure or modification.
Summary
What happened
Uncontrolled resource consumption in MLflow 2.13.2 and earlier allows remote attackers to make the tracking UI unresponsive. Experiment creation and rename paths accept names containing arbitrarily many integers, while creation also accepts an unbounded artifact_location value. A network-reachable tracking server must accept a crafted experiment operation; the oversized metadata can hang UI rendering without reported data disclosure or modification.
The record
- CVE
- CVE-2024-6838
- Published
- Mar 20, 2025
- Updated
- Mar 20, 2025
- Vendor
- MLflow Project
- Product
- MLflow
- Classifications
- CWE-400, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 20, 2025CVE publishedPublication date reported by the CVE source.
- Mar 20, 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 <=latest
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