Local File Inclusion (LFI) via Scheme Confusion in mlflow/mlflow
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| mlflow | mlflow/mlflow | affected |
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2024-1218 | mlflow/mlflow is vulnerable to Local File Inclusion (LFI) due to improper parsing of URIs, allowing attackers to bypass checks and read arbitrary files on the system. The issue arises from the 'is_local_uri' function's failure to properly handle URIs with empty or 'file' schemes, leading to the misclassification of URIs as non-local. Attackers can exploit this by crafting malicious model versions with specially crafted 'source' parameters, enabling the reading of sensitive files within at least two directory levels from the server's root. |
Github GHSA |
GHSA-hq88-wg7q-gp4g | mlflow vulnerable to Path Traversal |
No CVSS v4.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.733% probability within 30 days)
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Lfprojects
Lfprojects mlflow |
|
| Weaknesses | CWE-22 | |
| CPEs | cpe:2.3:a:lfprojects:mlflow:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Lfprojects
Lfprojects mlflow |
|
| Metrics |
cvssV3_1
|