CVE-2024-37058: High severity mlflow vulnerability
Published Jun 4, 2024
·Updated
Deserialization of untrusted data can occur in versions of the MLflow platform running version 2.5.0 or newer, enabling a maliciously uploaded Langchain AgentExecutor model to run arbitrary code on an end user’s system when interacted with.
Affected Software
2 affected components
pip/mlflow>=2.5.0<=2.14.1
Lfprojects Mlflow>=2.5.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-37058?
CVE-2024-37058 is considered a high severity vulnerability due to its potential to allow arbitrary code execution.
2
How do I fix CVE-2024-37058?
To mitigate CVE-2024-37058, it is recommended to upgrade MLflow to a version newer than 2.14.1.
3
What versions of MLflow are affected by CVE-2024-37058?
CVE-2024-37058 affects MLflow versions 2.5.0 through 2.14.1.
4
What kind of attack does CVE-2024-37058 enable?
CVE-2024-37058 enables an attacker to execute arbitrary code on an end user’s system through maliciously uploaded models.
5
What is the cause of CVE-2024-37058?
CVE-2024-37058 is caused by the deserialization of untrusted data within the MLflow platform.