{"answers":{"affected":"4 open source packages ship an affected version, including mlflow. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-3099 exists.","fix":"Upgrade mlflow to 2.11.3 or later.","what":"CVE-2024-3099 is a medium-severity vulnerability in Lfprojects Mlflow, published on 6 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-3099 and fix it if it is affected.\n\nWhat it is: CVE-2024-3099 is a medium-severity vulnerability in Lfprojects Mlflow, published on 6 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-3099 exists.\n\nAffected packages and fixed versions:\n- mlflow (Bitnami): affected all versions; no fix listed\n- mlflow (PyPI): affected all versions; fixed in 2.11.3\n- mlflow (PyPI): affected all versions; fixed in 2.11.3\n- mlflow (PyPI): affected all versions; fixed in 2.11.3\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-3099/ (Markdown: https://insights.sbomify.com/CVE-2024-3099/index.md)","id":"CVE-2024-3099","markdown":"https://insights.sbomify.com/CVE-2024-3099/index.md","name":"CVE-2024-3099","record":{"aliases":["BIT-mlflow-2024-3099","GHSA-8f8q-q2j7-7j2m","PYSEC-2026-1645"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"MLflow machine learning library","requires_auth":"low_privilege","summary":"Attackers can create duplicate model names via URL encoding, causing denial of service or data poisoning for authenticated users.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"mlflow","vendor":"lfprojects"}],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L","version":"3.0"},"cwes":[{"id":"CWE-475","name":"Undefined Behavior for Input to API"}],"description":"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.","ecosystems":["Bitnami","PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Denial of Service and Data Model Poisoning via URL Encoding in mlflow/mlflow","id":"CVE-2024-3099","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"lfprojects:mlflow","products":["lfprojects:mlflow"],"type":"business_logic","year":"2024"},"n_packages":4,"n_references":1,"next":{"headline":"Memory corruption in 100w Gen 3 Laptop (Lenovo) BIOS","id":"CVE-2024-3100"},"packages":[{"ecosystem":"Bitnami","fixed":[],"introduced":[],"last_affected":[],"package":"mlflow","purl":"pkg:bitnami/mlflow","source":"BIT-mlflow-2024-3099"},{"ecosystem":"PyPI","fixed":["2.11.3"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":null,"source":"GHSA-8f8q-q2j7-7j2m"},{"ecosystem":"PyPI","fixed":["2.11.3"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":"pkg:pypi/mlflow","source":"GHSA-8f8q-q2j7-7j2m"},{"ecosystem":"PyPI","fixed":["2.11.3"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":"pkg:pypi/mlflow","source":"PYSEC-2026-1645"}],"prev":{"headline":"Prompt Injection leading to Arbitrary Code Execution in run-llama/llama_index","id":"CVE-2024-3098"},"products":["mlflow/mlflow"],"published":"2024-06-06","related":[{"cvss_score":9.3,"headline":"MLflow Server-Side Request Forgery","id":"CVE-2026-64849","kev_date_added":"2026-08-19","published":"2026-08-17"},{"cvss_score":10,"headline":"Command Injection in mlflow/mlflow","id":"CVE-2025-15379","kev_date_added":null,"published":"2026-03-30"},{"cvss_score":10,"headline":"Remote Code Execution due to Full Controlled File Write in mlflow/mlflow","id":"CVE-2024-0520","kev_date_added":null,"published":"2024-06-06"},{"cvss_score":10,"headline":"Path Traversal: '\\..\\filename'","id":"CVE-2023-6977","kev_date_added":null,"published":"2023-12-20"},{"cvss_score":10,"headline":"Improper Neutralization of Special Elements Used in a Template Engine in mlflow/mlflow","id":"CVE-2023-6709","kev_date_added":null,"published":"2023-12-12"},{"cvss_score":10,"headline":"MLflow Arbitrary File Upload","id":"CVE-2023-6015","kev_date_added":null,"published":"2023-11-16"},{"cvss_score":10,"headline":"MLflow Arbitrary File Write","id":"CVE-2023-6018","kev_date_added":null,"published":"2023-11-16"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-01","vendors":["mlflow"]},"summary":"Attackers can create duplicate model names via URL encoding, causing denial of service or data poisoning for authenticated users.","url":"https://insights.sbomify.com/CVE-2024-3099/"}