CVE-2024-2928 in the critical feed json
Local File Inclusion (LFI) via URI Fragment Parsing in mlflow/mlflow
published 2024-06-06 2 y ago modified 2026-09-08 2 mo ago also BIT-mlflow-2024-2928 , EUVD-2024-2083 , GHSA-j46q-5pxx-8vmw , PYSEC-2024-242
- cvss
- 7.5
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 21.8%
- EPSS 21.8% chance of exploitation in 30 days, percentile 97%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
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.
Patch / fix
- pypi mlflow 2.11.3
- bitnami mlflow 2.11.3
- mlflow mlflow/mlflow 2.11.3
- lfprojects mlflow 2.11.3
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
21.85% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Nuclei template MLflow < 2.11.3 - Path Traversal nuclei detection template
- huntr.com https://huntr.com/bounties/19bf02d7-6393-4a95-b9d0-d6d4d2d8c298 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| OSV | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | mlflow | <2.11.3 |
2.11.3 |
| bitnami | mlflow | <2.11.3 |
2.11.3 |
Affected products
- mlflow mlflow/mlflow
- lfprojects mlflow
Classification
References
-
github.com
/mlflow/mlflow/commit/96f0b573a73d8eedd6735a2ce26e08859527be07
web, patch
-
huntr.com
/bounties/19bf02d7-6393-4a95-b9d0-d6d4d2d8c298
web, exploit, issue-tracking, patch, third-party-advisory, advisory, evidence, report
-
nvd.nist.gov
/vuln/detail/CVE-2024-2928
advisory, web
-
github.com
/mlflow/mlflow
package
-
github.com
/pypa/advisory-database/tree/main/vulns/mlflow/PYSEC-2024-242.yaml
web
-
github.com
/advisories/GHSA-j46q-5pxx-8vmw
advisory
Sources
- CVE List CVE-2024-2928
- GitHub Advisory GHSA-j46q-5pxx-8vmw
- NVD CVE-2024-2928
- OSV BIT-mlflow-2024-2928
- OSV PYSEC-2024-242
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.