{"answers":{"affected":"4 open source packages ship an affected version, including mlflow. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-6015 in the wild and no public exploit code.","fix":"Upgrade mlflow to 2.8.1 or later.","what":"CVE-2023-6015 is a critical vulnerability in Lfprojects Mlflow, published on 16 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-6015 and fix it if it is affected.\n\nWhat it is: CVE-2023-6015 is a critical vulnerability in Lfprojects Mlflow, published on 16 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-6015 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mlflow (Bitnami): affected all versions; fixed in 2.8.1\n- mlflow (PyPI): affected all versions; fixed in 2.8.1\n- mlflow (PyPI): affected all versions; fixed in 2.8.1\n- mlflow (PyPI): affected all versions; fixed in 2.8.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-2023-6015/ (Markdown: https://insights.sbomify.com/CVE-2023-6015/index.md)","id":"CVE-2023-6015","markdown":"https://insights.sbomify.com/CVE-2023-6015/index.md","name":"CVE-2023-6015","record":{"aliases":["BIT-mlflow-2023-6015","GHSA-f798-qm4r-23r5","PYSEC-2026-420"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"MLflow machine learning library","requires_auth":"none","summary":"Attackers can upload arbitrary files to the MLflow server, potentially leading to code execution or data modification.","user_interaction":"not_required","vuln_class":"file_upload"},"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:N","version":"3.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"MLflow allowed arbitrary files to be PUT onto the server.","ecosystems":["Bitnami","PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"MLflow Arbitrary File Upload","id":"CVE-2023-6015","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"lfprojects:mlflow","products":["lfprojects:mlflow"],"type":"file_upload","year":"2023"},"n_packages":4,"n_references":1,"next":{"headline":"H2O Remote Code Execution via POJO Model Import","id":"CVE-2023-6016"},"packages":[{"ecosystem":"Bitnami","fixed":["2.8.1"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":"pkg:bitnami/mlflow","source":"BIT-mlflow-2023-6015"},{"ecosystem":"PyPI","fixed":["2.8.1"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":null,"source":"GHSA-f798-qm4r-23r5"},{"ecosystem":"PyPI","fixed":["2.8.1"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":"pkg:pypi/mlflow","source":"GHSA-f798-qm4r-23r5"},{"ecosystem":"PyPI","fixed":["2.8.1"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":"pkg:pypi/mlflow","source":"PYSEC-2026-420"}],"prev":{"headline":"MLflow Authentication Bypass","id":"CVE-2023-6014"},"products":["mlflow/mlflow"],"published":"2023-11-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 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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-02","vendors":["mlflow"]},"summary":"Attackers can upload arbitrary files to the MLflow server, potentially leading to code execution or data modification.","url":"https://insights.sbomify.com/CVE-2023-6015/"}