{"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-0520 exists.","fix":"Upgrade mlflow to a fixed version for your release line: 2.9.1 or 2.9.0.","what":"CVE-2024-0520 is a critical path traversal vulnerability in Lfprojects Mlflow, published on 6 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-0520 and fix it if it is affected.\n\nWhat it is: CVE-2024-0520 is a critical path traversal vulnerability in Lfprojects Mlflow, published on 6 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-0520 exists.\n\nAffected packages and fixed versions:\n- mlflow (Bitnami): affected all versions; fixed in 2.9.1\n- mlflow (PyPI): affected all versions; fixed in 2.9.0\n- mlflow (PyPI): affected all versions; fixed in 2.9.0\n- mlflow (PyPI): affected all versions; fixed in 2.9.0\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-0520/ (Markdown: https://insights.sbomify.com/CVE-2024-0520/index.md)","id":"CVE-2024-0520","markdown":"https://insights.sbomify.com/CVE-2024-0520/index.md","name":"CVE-2024-0520","record":{"aliases":["BIT-mlflow-2024-0520","GHSA-5q6c-ffvg-xcm9","PYSEC-2024-239"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"MLflow library","requires_auth":"none","summary":"Attackers can achieve remote code execution via arbitrary file write in MLflow by exploiting path traversal in dataset loading.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"mlflow","vendor":"lfprojects"}],"cvss":{"score":10,"severity":"critical","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"A vulnerability in mlflow/mlflow version 8.2.1 allows for remote code execution due to improper neutralization of special elements used in an OS command ('Command Injection') within the `mlflow.data.http_dataset_source.py` module. Specifically, when loading a dataset from a source URL with an HTTP scheme, the filename extracted from the `Content-Disposition` header or the URL path is used to generate the final file path without proper sanitization. This flaw enables an attacker to control the file path fully by utilizing path traversal or absolute path techniques, such as '../../tmp/poc.txt' or '/tmp/poc.txt', leading to arbitrary file write. Exploiting this vulnerability could allow a malicious user to execute commands on the vulnerable machine, potentially gaining access to data and model information. The issue is fixed in version 2.9.0.","ecosystems":["Bitnami","PyPI"],"exploits":{"exploitdb":0,"first_seen":"2025-08-18","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-08-18T13:54:02Z","kind":"github_poc","ref":"https://github.com/chan-068/CVE-2024-0520_try","stars":0,"title":null}],"tier":"weaponised"},"has_fix":true,"headline":"Remote Code Execution due to Full Controlled File Write in mlflow/mlflow","id":"CVE-2024-0520","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"lfprojects:mlflow","products":["lfprojects:mlflow"],"type":"path_traversal","year":"2024"},"n_packages":4,"n_references":2,"next":{"headline":"Code Injection in paddlepaddle/paddle","id":"CVE-2024-0521"},"packages":[{"ecosystem":"Bitnami","fixed":["2.9.1"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":"pkg:bitnami/mlflow","source":"BIT-mlflow-2024-0520"},{"ecosystem":"PyPI","fixed":["2.9.0"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":null,"source":"GHSA-5q6c-ffvg-xcm9"},{"ecosystem":"PyPI","fixed":["2.9.0"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":"pkg:pypi/mlflow","source":"GHSA-5q6c-ffvg-xcm9"},{"ecosystem":"PyPI","fixed":["2.9.0"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":"pkg:pypi/mlflow","source":"PYSEC-2024-239"}],"prev":{"headline":"Google Chromium V8 Out-of-Bounds Memory Access","id":"CVE-2024-0519"},"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":"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-15","vendors":["mlflow"]},"summary":"Attackers can achieve remote code execution via arbitrary file write in MLflow by exploiting path traversal in dataset loading.","url":"https://insights.sbomify.com/CVE-2024-0520/"}