Cyber Resilience

CVE-2023-6831

Path Traversal in Lfprojects Mlflow ≤ 2.9.2

Public PoCPath Traversal
Published
15 December 2023
Modified
21 November 2024
Patch / advisory
View advisory
CVSS Score v3.1 8.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
EPSS Score 0.033 87th percentile
Risk Priority 85 floored blend · peak EPSS

Summary

CVE-2023-6831 is a high-severity Path Traversal: '\..\filename' (CWE-29) vulnerability in Lfprojects Mlflow. Its CVSS base score is 8.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 13% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

This vulnerability is AI-related — categorised as Other AI Platforms; in the Other ATLAS/OWASP Terms risk domain.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2023-6831 is a path traversal vulnerability, identified as CWE-29 and CWE-22, that affects the mlflow/mlflow GitHub repository in versions prior to 2.9.2. The flaw carries a CVSS 3.1 score of 8.1 and permits traversal sequences such as '\..\filename' that can be supplied over the network.

An authenticated attacker with low privileges can exploit the issue without user interaction to modify or delete files on the server, producing high integrity and availability impact while leaving confidentiality unaffected. The attack surface is network-reachable and requires only limited complexity to trigger.

References point to commits that resolve the traversal flaw and to the associated huntr.dev bounty report; these indicate that upgrading to MLflow 2.9.2 or later eliminates the exposure.

The EPSS score rose from lower values after disclosure to a peak of 0.8089 on 2025-12-11 before receding to the current 0.7398, demonstrating increased exploitation interest that warrants renewed attention for MLflow deployments.

OWASP Top 10 for Web (2025)

A01:2025 Broken Access Control

EU & UK References

Vulnerability Data

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

CWE(s)
CWE-29CWE-22

AI Security AnalysisAI

AI Category
Other AI Platforms
Risk Domain
Other ATLAS/OWASP Terms
OWASP Top 10 for LLMs 2025
None mapped
Classification Reason
MLflow is an open-source platform for managing the end-to-end machine learning lifecycle, including tracking experiments, packaging code, and deploying models, fitting under 'Other Platforms' as it is not a framework, library, or specialized AI tool.

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
attack.mitre.org →
T1083 File and Directory Discovery Discovery
Adversaries may enumerate files and directories or may search in specific locations of a host or network share for certain information within a file system.
attack.mitre.org →
T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-3573Same product: Lfprojects Mlflow
CVE-2024-2928Same product: Lfprojects Mlflow
CVE-2024-3848Same product: Lfprojects Mlflow
CVE-2023-1177Same product: Lfprojects Mlflow
CVE-2025-15036Same product: Lfprojects Mlflow
CVE-2024-1483Same product: Lfprojects Mlflow
CVE-2024-0520Same product: Lfprojects Mlflow
CVE-2024-1558Same product: Lfprojects Mlflow
CVE-2024-1560Same product: Lfprojects Mlflow
CVE-2024-1593Same product: Lfprojects Mlflow

Affected Assets

lfprojects
mlflow
≤ 2.9.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V5.3.2

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

SI-10 Information Input Validation
addresses: CWE-22

Validates pathnames and filenames to prevent traversal outside intended directories.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and path sanitization that block this traversal vector.

PR.PS-02 partial match
prevents

Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.

PR.AA-05 none match
prevents

PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can discover path-traversal flaws but does not itself prevent them in production code.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate input validation and path canonicalization to block traversal sequences.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles include directory sandboxing and safe file-access design that mitigate path traversal.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly require neutralizing path traversal sequences such as '\..\filename'.

A.8.3 Information access restriction partial match
mitigates

Information access restriction limits which files an application may read or write.

References