First published: Thu May 16 2024(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.
Credit: security@huntr.dev security@huntr.dev
Affected Software | Affected Version | How to fix |
---|---|---|
pip/mlflow | >=2.9.2<2.12.1 | 2.12.1 |
MLflow | <2.12.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-3848 is classified as a high-severity vulnerability due to its potential to allow unauthorized access to sensitive files.
To fix CVE-2024-3848, upgrade to mlflow version 2.12.1 or higher immediately.
CVE-2024-3848 is caused by improper handling of artifact URLs that allows for path traversal via the '#' character in URL fragments.
CVE-2024-3848 affects mlflow versions prior to 2.12.1.
Yes, CVE-2024-3848 is a bypass for the previously addressed CVE-2023-6909.