{"answers":{"affected":"4 open source packages ship an affected version, including mlflow. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-27134 in the wild and no public exploit code.","fix":"Upgrade mlflow to 2.16.0 or later.","what":"CVE-2024-27134 is a high-severity vulnerability in Lfprojects Mlflow, published on 25 Nov 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-27134 and fix it if it is affected.\n\nWhat it is: CVE-2024-27134 is a high-severity vulnerability in Lfprojects Mlflow, published on 25 Nov 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-27134 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mlflow (Bitnami): affected all versions; fixed in 2.16.0\n- mlflow (PyPI): affected all versions; fixed in 2.16.0\n- mlflow (PyPI): affected all versions; fixed in 2.16.0\n- mlflow (PyPI): affected all versions; fixed in 2.16.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-27134/ (Markdown: https://insights.sbomify.com/CVE-2024-27134/index.md)","id":"CVE-2024-27134","markdown":"https://insights.sbomify.com/CVE-2024-27134/index.md","name":"CVE-2024-27134","record":{"aliases":["BIT-mlflow-2024-27134","GHSA-qpgc-w4mg-6v92","PYSEC-2024-224"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"MLflow machine learning library","requires_auth":"none","summary":"Local attackers can escalate privileges via a race condition in MLflow's spark_udf API due to excessive directory permissions.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"JFROG","cpe":[{"product":"mlflow","vendor":"lfprojects"}],"cvss":{"score":7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-367","name":"Time-of-check Time-of-use (TOCTOU) Race Condition"},{"id":"CWE-276","name":"Incorrect Default Permissions"}],"description":"Excessive directory permissions in MLflow leads to local privilege escalation when using spark_udf. This behavior can be exploited by a local attacker to gain elevated permissions by using a ToCToU attack. The issue is only relevant when the spark_udf() MLflow API is called.","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":"Excessive directory permissions in MLflow leads to local privilege escalation when using spark_udf","id":"CVE-2024-27134","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"lfprojects:mlflow","products":["lfprojects:mlflow"],"type":"privilege_escalation","year":"2024"},"n_packages":4,"n_references":1,"next":{"headline":"Apache Pulsar: Improper Input Validation in Pulsar Function Worker allows Remote Code Execution","id":"CVE-2024-27135"},"packages":[{"ecosystem":"Bitnami","fixed":["2.16.0"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":"pkg:bitnami/mlflow","source":"BIT-mlflow-2024-27134"},{"ecosystem":"PyPI","fixed":["2.16.0"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":null,"source":"GHSA-qpgc-w4mg-6v92"},{"ecosystem":"PyPI","fixed":["2.16.0"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":"pkg:pypi/mlflow","source":"GHSA-qpgc-w4mg-6v92"},{"ecosystem":"PyPI","fixed":["2.16.0"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":"pkg:pypi/mlflow","source":"PYSEC-2024-224"}],"prev":{"headline":"Insufficient sanitization in MLflow leads to XSS when running a recipe that uses an untrusted dataset.","id":"CVE-2024-27133"},"products":["lfprojects:mlflow"],"published":"2024-11-25","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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-11-25","vendors":["lfprojects"]},"summary":"Local attackers can escalate privileges via a race condition in MLflow's spark_udf API due to excessive directory permissions.","url":"https://insights.sbomify.com/CVE-2024-27134/"}