CVE-2024-2928
A public proof of concept exists; no exploitation attested.
- Published2024-06-06
- Fixed in2.11.3
- WeaknessCWE-22 · CWE-29
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
A Local File Inclusion (LFI) vulnerability was identified in mlflow/mlflow, specifically in version 2.9.2, which was fixed in version 2.11.3. This vulnerability arises from the application's failure to properly validate URI fragments for directory traversal sequences such as '../'. An attacker can exploit this flaw by manipulating the fragment part of the URI to read arbitrary files on the local file system, including sensitive files like '/etc/passwd'. The vulnerability is a bypass to a previous patch that only addressed similar manipulation within the URI's query string, highlighting the need for comprehensive validation of all parts of a URI to prevent LFI attacks.
Timeline
dates in UTC- 2024-06-0619:15CVE publishedNVD
Versions per branch
NVD · CISA-ADP · OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2.11 | < 2.11.3 | 2.11.3 | NVD · CISA-ADP · OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Products declared by the CNA1 product
As @huntr_ai, the CNA that assigned this CVE, declared them in the CVE record; versions as written.
- mlflow/mlflowAffected
- < 2.11.3fixed in 2.11.3custom
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2024-06-06
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Packages
- mlflowTuxCare:PyPIfrom 2.9.1.post0 · fixed in 2.9.1.post2+tuxcare
Fix
- Update Lfprojects mlflow to 2.11.3
Advisories and patches
- github.comPatch
- huntr.comPatch
Detection
read 2026-11-01 01:02 UTC- Nuclei template
- available ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- PoC-in-GitHub2 repositories, unverifiedknown since 2026-11-01nuridincersaygili/CVE-2024-2928rain321654/sjtu_CVE-2024-2928
- Metasploit modules
- none listed Metasploit Framework
Sources
- CISA-ADPSSVC decisionnone2024-06-06
- NVDCVSS 3.17.5read 2026-10-23
- CNACVSS 3.07.5known since 2026-10-23
- CNAweakness (CWE)CWE-29known since 2026-10-23
- NVDweakness (CWE)CWE-22read 2026-10-23
- FIRST EPSSEPSS score21.8 %read 2026-11-18
- PoC-in-GitHubproof of concept2known since 2026-11-01
- ProjectDiscoverydetectionread 2026-11-18
- OSVaffected packages—
- GitHub AdvisoriesadvisoryHIGH2024-06-06
Identifiers
- BIT-mlflow-2024-2928same flawBitnami · Apache-2.0
- EUVD-2024-2083same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-j46q-5pxx-8vmwsame flawGitHub Advisory Database · CC-BY-4.0
- PYSEC-2024-242same flawPyPA Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Published
- 2024-06-06
- Last Modified
- 2026-06-17
- NVD status
- Modified
- GitHub Advisory
- GHSA-j46q-5pxx-8vmw
Frequently asked questions
What is CVE-2024-2928?
Is CVE-2024-2928 actively exploited?
What is the CVSS score for CVE-2024-2928?
Running mlflow? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-j46q-5pxx-8vmw
- Nuclei templates · MIT
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OSV.dev · Per record, as its publisher states it: each row carries the label in sourceLicense when one is served
- PoC-in-GitHub · CC0-1.0
- CISA Vulnrichment · CC0-1.0