CVE-2024-3848 — A path traversal vulnerability exists in mlflow/mlflow version 2

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 i

01What is this vulnerability?

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…

02Affected products

Vendor	Product	Versions
mlflow	mlflow/mlflow	unspecified

03Active exploitation status

Not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog. EPSS is the best forward-looking signal — see the EPSS row above.

04Recommended remediation

• Patch to a fixed version listed in the vendor advisory (see references below).
• Mitigate with WAF rules, network egress filters, or feature flags where the patch is not yet available.
• Hunt historical logs for exploitation indicators — see Detection signatures below.

05Technical details

For the full vendor write-up, exploit chains, and reference implementations, see the references list in section 09.

06Detection signatures

Open the Sigma generator with a pre-filled prompt for this CVE to draft a starting detection in your stack of choice:

Open in Sigma generator →

07Related CVEs

08Timeline

• Published: 2024-05-16T09:03:47.178Z
• Last modified: 2024-08-01T20:26:57.075Z

09References

• huntr.com — https://huntr.com/bounties/8d5aadaa-522f-4839-b41b-d7da362dd610
• github.com — https://github.com/mlflow/mlflow/commit/f8d51e21523238280ebcfdb378612afd7844eca8