CVE-2024-37053: High severity mlflow vulnerability
Published Jun 4, 2024
·Updated
Deserialization of untrusted data can occur in versions of the MLflow platform running version 1.1.0 or newer, enabling a maliciously uploaded scikit-learn model to run arbitrary code on an end user’s system when interacted with.
Affected Software
2 affected components
pip/mlflow>=1.1.0<=2.14.1
Lfprojects Mlflow>=1.1.0
Event History
Jun 4, 2024
CVE Published
via MITRE·12:00 PM
Data Sourced
via MITRE·12:00 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-37053?
The severity of CVE-2024-37053 is classified as critical due to its potential to allow arbitrary code execution.
2
How do I fix CVE-2024-37053?
To fix CVE-2024-37053, upgrade your MLflow platform to a version later than 2.14.1 that is not affected.
3
Which versions of MLflow are affected by CVE-2024-37053?
MLflow versions from 1.1.0 to 2.14.1 are affected by CVE-2024-37053.
4
What type of vulnerability is CVE-2024-37053?
CVE-2024-37053 is a deserialization vulnerability that can be exploited by untrusted data.
5
What could be the impact of CVE-2024-37053 on my system?
Exploitation of CVE-2024-37053 could allow a maliciously uploaded model to execute arbitrary code on the affected system.