First published: Tue Apr 16 2024(Updated: )
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.
Credit: security@huntr.dev security@huntr.dev
Affected Software | Affected Version | How to fix |
---|---|---|
pip/mlflow | <2.10.0 | 2.10.0 |
MLflow | <2.10.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-3573 is classified as a medium severity vulnerability due to the risk of Local File Inclusion allowing attackers to read arbitrary files.
To fix CVE-2024-3573, update the mlflow package to version 2.10.0 or later.
CVE-2024-3573 is a Local File Inclusion (LFI) vulnerability affecting the mlflow software.
CVE-2024-3573 is caused by improper parsing of URIs in the 'is_local_uri' function, which fails to handle certain URI schemes correctly.
All versions of mlflow prior to 2.10.0 are affected by CVE-2024-3573.