CVE-2024-37060: High severity mlflow vulnerability
Published Jun 4, 2024
·Updated
Deserialization of untrusted data can occur in versions of the MLflow platform running version 1.27.0 or newer, enabling a maliciously crafted Recipe to execute arbitrary code on an end user’s system when run.
Affected Software
3 affected components
pip/mlflow>=1.27.0<=2.13.1
pip/mlflow>=1.27.0<=2.14.1
Lfprojects Mlflow>=1.27.0
Event History
Jun 4, 2024
CVE Published
via MITRE·12:02 PM
Data Sourced
via MITRE·12:02 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-37060?
CVE-2024-37060 is classified as a critical vulnerability due to its potential to execute arbitrary code on a user's system.
2
How do I fix CVE-2024-37060?
To mitigate CVE-2024-37060, upgrade to a version of MLflow earlier than 1.27.0 or apply security patches if available.
3
What versions of MLflow are affected by CVE-2024-37060?
CVE-2024-37060 affects MLflow versions starting from 1.27.0 up to 2.14.1 inclusively.
4
What type of vulnerability is CVE-2024-37060?
CVE-2024-37060 is a deserialization vulnerability that can occur with untrusted data in MLflow.
5
What systems are at risk due to CVE-2024-37060?
Any system running affected versions of MLflow is at risk of arbitrary code execution if exposed to crafted Recipes.