CVE-2024-37056: High severity mlflow vulnerability
Published Jun 4, 2024
·Updated
Deserialization of untrusted data can occur in versions of the MLflow platform running version 1.23.0 or newer, enabling a maliciously uploaded LightGBM scikit-learn model to run arbitrary code on an end user’s system when interacted with.
Affected Software
3 affected components
pip/mlflow>=1.23.0<=2.13.1
pip/mlflow>=1.23.0<=2.14.1
Lfprojects Mlflow>=1.23.0
Event History
Jun 4, 2024
CVE Published
via MITRE·12:01 PM
Data Sourced
via MITRE·12:01 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·12:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·12:15 PM
Affected Software
Advisory Published
via GitHub·12:31 PM
Frequently Asked Questions
1
What is the severity of CVE-2024-37056?
CVE-2024-37056 is considered a high severity vulnerability due to the potential for arbitrary code execution.
2
How do I fix CVE-2024-37056?
To fix CVE-2024-37056, upgrade to a version of MLflow that is newer than 2.14.1.
3
What types of attacks are possible with CVE-2024-37056?
CVE-2024-37056 allows a malicious user to upload a LightGBM scikit-learn model that can execute arbitrary code.
4
Which versions of MLflow are affected by CVE-2024-37056?
MLflow versions from 1.23.0 up to 2.14.1 are affected by CVE-2024-37056.
5
How does CVE-2024-37056 impact user systems?
CVE-2024-37056 allows untrusted data deserialization, leading to possible arbitrary code execution on user systems.