9.3
Critique
CVE-2024-3573 mlflow/mlflow is vulnerable to Local File Inclusion (LFI) due to improper parsing of URIs, allowing attackers to…
Description
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.
Produits et versions touchés
| Produit | Versions touchées | Corrigé en |
|---|---|---|
| MLflow 2.10 | premières → < 2.10.0 | 2.10.0 |
| mlflow/mlflow 2.10 | premières → < 2.10.0 | 2.10.0 |
Autres CVE de MLflow
Les 20 CVE de MLflow →
CVE-2025-52967
gateway_proxy_handler in MLflow before 3.1.0 lacks gateway_path validation
5.8
Moyenne
CVE-2024-27134
Excessive directory permissions in MLflow leads to local privilege escalation when using spark_udf
7.0
Élevée
CVE-2024-2928
A Local File Inclusion (LFI) vulnerability was identified in mlflow/mlflow, specifically in version 2.9.2, which was…
7.5
Élevée
CVE-2024-3099
A vulnerability in mlflow/mlflow version 2.11.1 allows attackers to create multiple models with the same name by…
5.4
Moyenne