Local File Inclusion (LFI) via Scheme Confusion in mlflow/mlflow
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in MLflow 2.10.0.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| MLflow | MLflow | <2.10.0 | 2.10.0 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in MLflow, strongest first
Embed
A live severity badge for an advisory, README or ticket