{"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-1483 exists.","fix":"Upgrade mlflow to 2.12.1 or later.","what":"CVE-2024-1483 is a high-severity path traversal vulnerability in Lfprojects Mlflow, published on 16 Apr 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-1483 and fix it if it is affected.\n\nWhat it is: CVE-2024-1483 is a high-severity path traversal vulnerability in Lfprojects Mlflow, published on 16 Apr 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-1483 exists.\n\nAffected packages and fixed versions:\n- mlflow (Bitnami): affected all versions; fixed in 2.12.1\n- mlflow (PyPI): affected all versions; fixed in 2.12.1\n- mlflow (PyPI): affected all versions; fixed in 2.12.1\n- mlflow (PyPI): affected all versions; fixed in 2.12.1\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-1483/ (Markdown: https://insights.sbomify.com/CVE-2024-1483/index.md)","id":"CVE-2024-1483","markdown":"https://insights.sbomify.com/CVE-2024-1483/index.md","name":"CVE-2024-1483","record":{"aliases":["BIT-mlflow-2024-1483","GHSA-f82r-jj5r-6g97","PYSEC-2026-1650"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"MLflow library","requires_auth":"none","summary":"Attackers can read arbitrary files on the server by exploiting insufficient input validation in MLflow's artifact handling.","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":7.5,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"A path traversal vulnerability exists in mlflow/mlflow version 2.9.2, allowing attackers to access arbitrary files on the server. By crafting a series of HTTP POST requests with specially crafted 'artifact_location' and 'source' parameters, using a local URI with '#' instead of '?', an attacker can traverse the server's directory structure. The issue occurs due to insufficient validation of user-supplied input in the server's handlers.","ecosystems":["Bitnami","PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2024/CVE-2024-1483.yaml","stars":null,"title":"Mlflow \u003c 2.9.2 - Path Traversal"}],"tier":"weaponised"},"has_fix":true,"headline":"Path Traversal Vulnerability in mlflow/mlflow","id":"CVE-2024-1483","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":1,"next":{"headline":"Booking for Appointments and Events Calendar – Amelia \u003c= 1.0.98 - Reflected Cross-Site Scripting","id":"CVE-2024-1484"},"packages":[{"ecosystem":"Bitnami","fixed":["2.12.1"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":"pkg:bitnami/mlflow","source":"BIT-mlflow-2024-1483"},{"ecosystem":"PyPI","fixed":["2.12.1"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":null,"source":"GHSA-f82r-jj5r-6g97"},{"ecosystem":"PyPI","fixed":["2.12.1"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":"pkg:pypi/mlflow","source":"GHSA-f82r-jj5r-6g97"},{"ecosystem":"PyPI","fixed":["2.12.1"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":"pkg:pypi/mlflow","source":"PYSEC-2026-1650"}],"prev":{"headline":"Improper Authorization in GitHub Enterprise Server allowed unauthorized workflow execution","id":"CVE-2024-1482"},"products":["mlflow/mlflow"],"published":"2024-04-16","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)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-01","vendors":["mlflow"]},"summary":"Attackers can read arbitrary files on the server by exploiting insufficient input validation in MLflow's artifact handling.","url":"https://insights.sbomify.com/CVE-2024-1483/"}