CVE-2024-3099: medium-severity vulnerability in mlflow/mlflow
Denial of Service and Data Model Poisoning via URL Encoding in mlflow/mlflow
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 5.4epss 0.4%
A vulnerability in mlflow/mlflow version 2.11.1 allows attackers to create multiple models with the same name by exploiting URL encoding. This flaw can lead to Denial of Service (DoS) as an authenticated user might not be able to use the intended model, as it will open a different model each time. Additionally, an attacker can exploit this vulnerability to perform data model poisoning by creating a model with the same name, potentially causing an authenticated user to become a victim by using the poisoned model. The issue stems from inadequate validation of model names, allowing for the creation of models with URL-encoded names that are treated as distinct from their URL-decoded counterparts.
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
Affected products
mlflow · mlflow/mlflowRelated CVEs — mlflow/mlflow
In the same product, most dangerous first.
CVE-2023-6909HIGHPath Traversal: '\..\filename' in mlflow/mlflowEPSS 89.7%CVE-2023-1177CRITICALPath Traversal: '\..\filename' in mlflow/mlflowEPSS 69.7%CVE-2023-3765CRITICALAbsolute Path Traversal in mlflow/mlflowEPSS 67.3%CVE-2023-6018CRITICALMLflow Arbitrary File WriteEPSS 47.9%CVE-2024-3848HIGHPath Traversal Bypass in mlflow/mlflowEPSS 43.0%CVE-2024-2928HIGHLocal File Inclusion (LFI) via URI Fragment Parsing in mlflow/mlflowEPSS 21.8%