CVE-2024-3848: MLflow has a Local File Read/Path Traversal bypass
(updated )
A path traversal vulnerability exists in mlflow/mlflow version 2.11.0, identified as a bypass for the previously addressed CVE-2023-6909. The vulnerability arises from the application’s handling of artifact URLs, where a ‘#’ character can be used to insert a path into the fragment, effectively skipping validation. This allows an attacker to construct a URL that, when processed, ignores the protocol scheme and uses the provided path for filesystem access. As a result, an attacker can read arbitrary files, including sensitive information such as SSH and cloud keys, by exploiting the way the application converts the URL into a filesystem path. The issue stems from insufficient validation of the fragment portion of the URL, leading to arbitrary file read through path traversal.
References
- github.com/advisories/GHSA-rfqq-wq6w-72jm
- github.com/mlflow/mlflow
- github.com/mlflow/mlflow/commit/f8d51e21523238280ebcfdb378612afd7844eca8
- github.com/pypa/advisory-database/tree/main/vulns/mlflow/PYSEC-2024-244.yaml
- huntr.com/bounties/8d5aadaa-522f-4839-b41b-d7da362dd610
- nvd.nist.gov/vuln/detail/CVE-2024-3848
Code Behaviors & Features
Detect and mitigate CVE-2024-3848 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →