S4E just found a high-severity finding from top 10 tcp port service scan
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
high·Product Based Web Vulnerabilities·Updated Dec 3, 2024

CVE-2024-3848 Scanner

CVE-2024-3848 Scanner - Path Traversal vulnerability in mlflow

Est. Time~10 seconds
Scan TypeSingle Scan
Targetsdomain, ipv4, subdomain
CostFree
2.7k
Times Used
continuous scan runs
5.8k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
CVECVE-2024-3848
7.5
CVSShigh
Exploitable remotely over the internet · no authentication required.

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.

Attack Vector
Network
Privileges Req.
None
User Interaction
None
Affected
mlflow/mlflowby mlflow
AFFECTED< 2.12.1SAFE ✓≥ 2.12.1
mlflowby lfprojects
AFFECTED< 2.12.1SAFE ✓≥ 2.12.1
Updated Sep 10, 2026View on NVD →
Detail

Product Overview:

MLflow is an open-source platform designed for managing the machine learning lifecycle, including experimentation, reproducibility, and deployment. It is commonly used by data scientists and machine learning engineers to track, share, and manage their machine learning models. It provides tools to record and compare results, package code into reproducible runs, and manage deployments. MLflow supports multiple machine learning frameworks and integrates with various cloud platforms. The platform is widely adopted for end-to-end model management. However, it is important to note that vulnerabilities in MLflow could lead to security risks for users who rely on it for critical machine learning tasks.

Vulnerability Overview:

This vulnerability is a path traversal issue in MLflow versions prior to 2.11.0. The vulnerability arises from improper validation of URL fragments used in artifact URLs. An attacker can exploit this by inserting a '#' character into the URL, allowing the attacker's path to bypass the validation process. This could lead to the ability to access files outside the intended directory, including sensitive configuration files and SSH keys, posing a significant risk to system integrity and confidentiality. It was a bypass of the previously addressed CVE-2023-6909, which makes this vulnerability particularly impactful for older versions of MLflow.

Vulnerability Details:

The path traversal vulnerability exists in the way MLflow handles artifact URLs. When the application processes the URL, it fails to properly validate the fragment part of the URL after the '#' character. This allows an attacker to inject a path that is processed as a filesystem path, bypassing any restrictions on file access. The malicious URL could reference critical files, such as configuration files or private SSH keys, allowing attackers to disclose sensitive information. The vulnerability stems from insufficient validation of the fragment portion, and attackers can exploit this to access arbitrary files stored on the server. The attack is possible even if the user does not have authorized access to the system, making it a significant threat for unpatched systems.

Possible Effects:

If exploited, this vulnerability could lead to the unauthorized disclosure of sensitive data. Attackers may gain access to internal configuration files, SSH keys, or other critical information that could be used for further attacks or system compromise. The risk of information leakage could affect the security of entire systems relying on MLflow. This could result in data breaches, privilege escalation, or unauthorized access to cloud environments. Additionally, such vulnerabilities could undermine trust in the security of MLflow, potentially causing reputation damage for organizations using it.

REFERENCES

Solution Advice
  • Update the MLflow package to the latest version (2.12.1 or higher).
  • Ensure that proper validation is in place for all parts of the artifact URL, including fragments.
  • Review security configurations and restrict file access as necessary.
  • Regularly update software and monitor for potential security issues.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

11,000+ scanners. Free to start. No credit card required.

CVE-2024-3848 Scanner - Path Traversal vulnerability in mlflow | S4E