LF Projects MLflow 2.11.1
Approved changes feed: RSS · Atom
cpe:2.3:a:lfprojects:mlflow:2.11.1:*:*:*:*:*:*:*
part: a version: 2.11.1 update: *
| Vendor | Lfprojects (4544abc5-133d-544b-9bd5-895c4c487a16) |
|---|---|
| Product | Mlflow (5e81e7b0-7dac-5ba5-8d2f-b1ba6b55eb8a) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/mlflow/mlflow |
purl2cpe | 2026-06-01 10:17:49.978329 |
pkg:pypi/mlflow |
purl2cpe | 2026-06-01 10:17:49.978331 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-3099 |
vulnerable | 2026-06-03 14:56:23.372183 |
Denial of Service and Data Model Poisoning via URL Encoding in mlflow/mlflow
MEDIUM (5.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.
Published: 2024-06-06T18:08:16.402Z
Updated: 2024-08-01T19:32:42.675Z Reference links |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.