S4E just found a high-severity finding from cve-2025-58360 scanner
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
high·Product Based Web Vulnerabilities·Updated Feb 18, 2024

CVE-2023-6831 Scanner

Detects 'Path Traversal' vulnerability in mlflow affects v. prior to 2.9.2.

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-2023-6831
8.1
CVSShigh
Exploitable remotely over the internet · low-privilege account sufficient.

Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.9.2.

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

Vulnerability Overview

  • CVE Identifier: CVE-2023-6831
  • Vulnerable Component: mlflow application
  • Parameters Affected: File access and deletion endpoints
  • Issue: Path Traversal vulnerability allowing access to files outside of restricted directories.

Vulnerability Details

The CVE-2023-6831 vulnerability in the mlflow project before version 2.9.2 is a Path Traversal flaw that arises due to insufficient sanitization of user-supplied input. An attacker can exploit this vulnerability by crafting malicious requests containing directory traversal sequences (\..\filename). This exploitation allows the attacker to access, read, or manipulate files outside of the restricted directory that the web application intends to access. This vulnerability specifically affects the mlflow's artifact handling functionality, where artifacts are intended to be securely managed within specific directories. By exploiting the path traversal flaw, an attacker could manipulate URLs or POST data to escape out of the intended directory and potentially access sensitive files on the server, such as configuration files, source code, or even system files, depending on the server's file system permissions.

Possible Effects

The exploitation of the CVE-2023-6831 vulnerability can have several significant impacts on an organization:

  1. Data Breach: Sensitive data stored in files accessible to the mlflow application could be exposed to unauthorized users. This might include confidential business data, personal information of users, or credentials stored in configuration files.

  2. System Compromise: If system files or executables are accessed or modified, it could lead to a complete system compromise. An attacker could potentially escalate privileges or deploy malicious payloads, leading to further exploitation.

  3. Service Disruption: Manipulating or deleting critical files could disrupt the mlflow service or related applications, affecting availability and potentially leading to denial of service (DoS).

  4. Reputation Damage: A successful exploitation could damage the organization's reputation, leading to loss of trust among customers and users, which might have long-term effects on business operations and revenue.

  5. Regulatory and Compliance Implications: Data breaches involving personal or sensitive information could result in regulatory fines and legal challenges, especially if the organization is subject to data protection regulations like GDPR or HIPAA.

Why Choose S4E

S4E offers comprehensive security solutions, including the CVE-2023-6831 Scanner, to help organizations detect and address vulnerabilities efficiently. Our platform provides detailed reports, actionable insights, and expert support to enhance your security posture. By joining S4E, users gain access to advanced scanning technologies and a community committed to cybersecurity excellence.

References

Solution Advice

To mitigate the vulnerability and its potential effects, organizations are recommended to take the following actions:

  • Upgrade to Version 2.9.2: Immediately upgrade mlflow to version 2.9.2 or later to patch the vulnerability.
  • Access Control: Ensure that only trusted users have access to the mlflow application, as the exploitation requires authenticated access.
  • Monitor Access Logs: Regularly monitor access logs for any unusual access patterns or requests that might indicate exploitation attempts.
  • Regular Updates: Continuously monitor for updates and patches for mlflow and apply them promptly to protect against emerging threats.
  • Security Review: Conduct a thorough security review of the environment where mlflow is hosted to identify and mitigate any other 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-2023-6831 scanner - Path Traversal vulnerability in mlflow | S4E