CVE-2024-3848: Path Traversal Bypass in mlflow/mlflow
mlflow · mlflow/mlflow
Vendor fix available · Affected: mlflow/mlflow · Exploitation: check available, not yet exploited
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 98% of scored CVEs
DescriptionCVE.org
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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- mlflow · mlflow/mlflowbefore 2.12.1
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Check available, not yet exploited. A public nuclei template can confirm it on a system you are authorised to test.
- CISA KEV
- Not listed
- Public check
- Mlflow < 2.11.0 - Path Traversal · nuclei template in projectdiscovery/nuclei-templates
- Vendor
- mlflow
- Published
- May 2024
CoverageNo articles yet
No CyberSIXT article names CVE-2024-3848 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.