Platform
python
Component
mlflow
Fixed in
2.9.3
CVE-2024-1594 describes a path traversal vulnerability discovered in the MLflow project. This flaw allows attackers to potentially read sensitive files on the server by manipulating the artifact_location parameter during experiment creation. The vulnerability impacts MLflow versions 2.9.2 and earlier. A fix is available in a patched version of MLflow.
The path traversal vulnerability in MLflow allows an attacker to bypass intended access controls and read arbitrary files on the server. By crafting a malicious artifact_location URI containing a fragment component (#), an attacker can specify a path outside the intended artifact storage directory. This could expose sensitive configuration files, source code, or other data stored on the server. The potential impact extends to data confidentiality and could enable further exploitation if exposed files contain credentials or other sensitive information. The similarity to CVE-2023-6909 highlights the potential for similar attack patterns and the importance of thorough input validation.
CVE-2024-1594 was publicly disclosed on April 16, 2024. The vulnerability's similarity to CVE-2023-6909 suggests a potential for similar exploitation techniques. Currently, there are no reports of active exploitation campaigns targeting this vulnerability, but the availability of a public proof-of-concept increases the risk. The EPSS score is likely to be assessed as medium due to the ease of exploitation and potential impact.
Exploit Status
EPSS
0.21% (43% percentile)
CISA SSVC
CVSS Vector
The primary mitigation for CVE-2024-1594 is to upgrade to a patched version of MLflow that addresses the vulnerability. If upgrading immediately is not feasible, consider implementing input validation on the artifactlocation parameter to prevent the inclusion of fragment components (#). Additionally, restrict file system permissions to limit the attacker's ability to read arbitrary files, even if they manage to traverse the directory structure. After upgrading, verify the fix by attempting to create an experiment with a crafted artifactlocation URI containing a fragment component and confirming that the server rejects the request or redirects to the intended artifact storage location.
Actualice la biblioteca mlflow a la última versión disponible. Esto solucionará la vulnerabilidad de path traversal. Consulte las notas de la versión para obtener más detalles sobre la actualización.
Vulnerability analysis and critical alerts directly to your inbox.
CVE-2024-1594 is a Path Traversal vulnerability affecting MLflow versions 2.9.2 and earlier, allowing attackers to read arbitrary files by manipulating the artifact location URI.
You are affected if you are using MLflow version 2.9.2 or earlier. Upgrade to a patched version to mitigate the risk.
Upgrade to a patched version of MLflow. As a temporary workaround, implement input validation on the artifact_location parameter to prevent fragment components.
There are currently no confirmed reports of active exploitation, but the vulnerability is publicly known and a proof-of-concept may exist.
Refer to the MLflow security advisories and release notes on the MLflow GitHub repository for the latest information.
Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.
Upload your requirements.txt file and we'll tell you instantly if you're affected.