github.com
https://github.com/mlflow/mlflow CVE-2024-3848
HIGHNuclei
Path Traversal Bypass in mlflow/mlflow
Record summary
CVE-2024-3848 has a selected CVSS score of 7.5 (high); EIP currently links 1 Nuclei template.
Description
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.
Description source: CVE List
Exploitation context
Available material
- Nuclei templates
- 1
CISA SSVC decision
ExploitationPoC
AutomatableYes
Technical impactPartial
CISA Coordinator · SSVC 2.0.3 · Evaluated May 16, 2024 · Source: CVE List
Affected products and versions
3| Product | Source | Version range | Status |
|---|---|---|---|
Default status: unknown | CVE List | 2.11.0 to < 2.12.1 | affected |
mlflow/mlflowBrowse mlflow / mlflow/mlflow | CVE List | Before 2.12.1 | affected |
mlflowBrowse PyPI / mlflow | GitHub Advisory | 2.9.2 to < 2.12.1 · Fixed in 2.12.1 | affected |
Nuclei templates
1ProjectDiscoveryHIGHMlflow < 2.11.0 - Path TraversalCVSS 7.5
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.
Impact
Successful exploitation could be lead to disclose of sensitive information such as SSH Keys or Internal configurations.
Remediation
To fix this vulnerability, it is important to update the mlflow package to the latest version 2.12.1.
WeaknessesCWE-29
Authorsgy741
Template tagscvecve2024mlflowlfiintrusivelfprojectsvuln
CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CPE: cpe:2.3:a:lfprojects:mlflow:*:*:*:*:*:*:*:*
Shodan: http.title:"mlflow"
FOFA: title="mlflow"
FOFA: app="mlflow"
Google: intitle:"mlflow"
https://huntr.com/bounties/8d5aadaa-522f-4839-b41b-d7da362dd610 https://nvd.nist.gov/vuln/detail/CVE-2024-3848
Source: ProjectDiscovery
References
5github.com
https://github.com/mlflow/mlflow/commit/f8d51e21523238280ebcfdb378612afd7844eca8 github.com
https://github.com/pypa/advisory-database/tree/main/vulns/mlflow/PYSEC-2024-244.yaml huntr.com
https://huntr.com/bounties/8d5aadaa-522f-4839-b41b-d7da362dd610 nvd.nist.gov
https://nvd.nist.gov/vuln/detail/CVE-2024-3848