Atomicorp WAF Research Note: CVE-2024-3848

Mlflow < 2.11.0 - Path Traversal

CVE Details

• Already protected by existing Atomicorp WAF rules
• Protection status: Understanding Atomicorp WAF Protection Status
• CVE: CVE-2024-3848
• Name: Mlflow < 2.11.0 - Path Traversal
• Severity: High
• CVSS: 7.5 (v3.1) (High)
• CVSS version: 3.1
• CVSS source: N/A
• CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
  • Attack vector: Network
  • Attack complexity: Low
  • Privileges required: None
  • User interaction: None
  • Scope: Unchanged
  • Confidentiality impact: High
  • Integrity impact: None
  • Availability impact: None
• CWE: CWE-22 — Improper Limitation of a Pathname to a Restricted Directory (‘Path Traversal’), CWE-29 — Path Traversal: ‘..\filename’
• Related CAPEC attack patterns (via MITRE CWE relationships): CAPEC-126 (opens in a new tab) , CAPEC-64 (opens in a new tab) , CAPEC-76 (opens in a new tab) , CAPEC-78 (opens in a new tab) , CAPEC-79 (opens in a new tab)
• Vendor: lfprojects
• Vulnerable product: mlflow
• CVE published: 2024-05-16
• CVE last modified: 2026-06-17
• Affected versions (NVD configurations):
  • mlflow: < 2.12.1
• EPSS: 0.4328; 98.6th percentile (FIRST (opens in a new tab) )
• Latest Update: 2026-09-06
• Selected Rule IDs observed: 340007 , 340162 , 340163 , 390709
• Matching rules: 4; rules with blocking actions: 4
• Would-block Rule IDs: 340007 , 340162 , 340163 , 390709
• Request surfaces inspected: JSON request data, Request URI, Request argument names, Request arguments, Request filename, SOAP request data, XML request data

Vulnerability 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.

Recommended Actions

1. Maintain the observed Atomicorp protections. Keep your Atomicorp commercial rules current and confirm that the selected observed rules (340007 , 340162 , 340163 , 390709 ) have not been locally disabled. Atomicorp commercial rules are enabled by default. If you use Atomic WAF, review the applicable policy and rule settings.

2. Apply the vendor’s remediation. WAF protection is defense in depth and does not replace upgrading or following the affected vendor’s guidance.

   • Affected versions: mlflow mlflow/mlflow versions earlier than 2.12.1.
   • The CVE record does not include written upgrade or workaround instructions, but it does publish the following patch or mitigation reference:
     • Patch or mitigation information (opens in a new tab)

3. Validate after changes. Confirm rule updates are current, review WAF events for the affected application, and test application behavior after vendor upgrades, mitigations, or local policy changes.

Research Notes

Atomicorp WAF protections are designed around attack techniques and exploit behaviors, allowing existing protections to apply across multiple vulnerabilities without requiring a unique rule for every CVE.

Public Vulnerability References

• NVD (opens in a new tab)
• CVE Record (opens in a new tab)
• Patch or mitigation: https://github.com/mlflow/mlflow/commit/f8d51e21523238280ebcfdb378612afd7844eca8 (opens in a new tab)
• Exploit or technical research: https://huntr.com/bounties/8d5aadaa-522f-4839-b41b-d7da362dd610 (opens in a new tab)

Test or Research Source

• Source: http/cves/2024/CVE-2024-3848.yaml (opens in a new tab)
• Tags: cve, cve2024, intrusive, lfi, lfprojects, mlflow, vuln

Research Note Context

This research note documents exploit-technique analysis associated with this vulnerability and references Atomicorp WAF protections observed during engineering review, testing, or validation activities.

Atomicorp security controls are generally designed to identify and mitigate attack techniques and exploit behaviors rather than individual CVE identifiers. As a result, protections developed for one vulnerability may also apply to related attack variants and future vulnerabilities using similar techniques.

Learn More

Atomicorp develops commercially supported security technologies for web applications, servers, endpoints, workloads, and legacy enterprise platforms.

Organizations interested in protecting systems against exploit techniques associated with vulnerabilities such as this one can learn more about:

• Atomic ModSecurity Rules: commercially maintained WAF rules for ModSecurity deployments, including protections for web attacks, bots, scanners, malware, exploitation attempts, and emerging vulnerability classes.
• Atomic WAF: an enterprise web application firewall with Atomicorp rules, centralized management, reporting, authentication controls, and operational tooling.
• Atomic ModSecurity Integrator: a special licensing option for MSPs, MSSPs, OEMs, VARs, reverse proxy providers, and other integrators who want to incorporate Atomicorp ModSecurity rule technology into their own products or services.
• Atomic OSSEC: an enterprise OSSEC-based intrusion detection, compliance, and security monitoring platform.
• Atomic Protector: workload protection for Linux, web, cloud, data center, and hybrid environments.

For additional information, product evaluations, or technical discussions, visit https://www.atomicorp.com/ or https://modsecurity.io/ (opens in a new tab) .