CVE-2024-0520: Lfprojects Mlflow remote code execution (CVSS 8.8)

Description

A vulnerability in mlflow/mlflow version 8.2.1 allows for remote code execution due to improper neutralization of special elements used in an OS command ('Command Injection') within the `mlflow.data.http_dataset_source.py` module. Specifically, when loading a dataset from a source URL with an HTTP scheme, the filename extracted from the `Content-Disposition` header or the URL path is used to generate the final file path without proper sanitization. This flaw enables an attacker to control the file path fully by utilizing path traversal or absolute path techniques, such as '../../tmp/poc.txt' or '/tmp/poc.txt', leading to arbitrary file write. Exploiting this vulnerability could allow a malicious user to execute commands on the vulnerable machine, potentially gaining access to data and model information. The issue is fixed in version 2.9.0.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionRequired

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected products

Lfprojects Mlflow< 2.9.0

Remediation

Fixed in

Lfprojects Mlflow≥ 2.9.0

Patch & vendor advisories

References

https://github.com/mlflow/mlflow/commit/400c226953b4568f4361bc0a0c223511652c2b9dPatch
https://huntr.com/bounties/93e470d7-b6f0-409b-af63-49d3e2a26dbcExploitIssue TrackingPatchThird Party Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2024-0520 being actively exploited?

CVE-2024-0520 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 2.40%.

How severe is CVE-2024-0520?

CVE-2024-0520 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 2.40% probability of exploitation.

Which products are affected by CVE-2024-0520?

Affected products include Lfprojects Mlflow.

How do I fix CVE-2024-0520?

Upgrade affected software to a fixed version, for example Lfprojects Mlflow 2.9.0 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-0520 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo