{"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-2023-6568 exists.","fix":"Upgrade mlflow to a fixed version for your release line: 2.9.1 or 2.9.0.","what":"CVE-2023-6568 is a medium-severity cross-site scripting vulnerability in Lfprojects Mlflow, published on 7 Dec 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-6568 and fix it if it is affected.\n\nWhat it is: CVE-2023-6568 is a medium-severity cross-site scripting vulnerability in Lfprojects Mlflow, published on 7 Dec 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-6568 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.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-6568/ (Markdown: https://insights.sbomify.com/CVE-2023-6568/index.md)","id":"CVE-2023-6568","markdown":"https://insights.sbomify.com/CVE-2023-6568/index.md","name":"CVE-2023-6568","record":{"aliases":["BIT-mlflow-2023-6568","GHSA-vwhf-3v6x-wff8","PYSEC-2023-260"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"MLflow machine learning library","requires_auth":"none","summary":"Attackers can execute arbitrary JavaScript in victims' browsers by injecting malicious code into the Content-Type header of POST requests to MLflow.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"mlflow","vendor":"lfprojects"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"A reflected Cross-Site Scripting (XSS) vulnerability exists in the mlflow/mlflow repository, specifically within the handling of the Content-Type header in POST requests. An attacker can inject malicious JavaScript code into the Content-Type header, which is then improperly reflected back to the user without adequate sanitization or escaping, leading to arbitrary JavaScript execution in the context of the victim's browser. The vulnerability is present in the mlflow/server/auth/__init__.py file, where the user-supplied Content-Type header is directly injected into a Python formatted string and returned to the user, facilitating the XSS attack.","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/2023/CVE-2023-6568.yaml","stars":null,"title":"Mlflow - Cross-Site Scripting"}],"tier":"weaponised"},"has_fix":true,"headline":"Reflected XSS via Content-Type Header in mlflow/mlflow","id":"CVE-2023-6568","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"lfprojects:mlflow","products":["lfprojects:mlflow"],"type":"xss","year":"2023"},"n_packages":4,"n_references":2,"next":{"headline":"External Control of File Name or Path in h2oai/h2o-3","id":"CVE-2023-6569"},"packages":[{"ecosystem":"Bitnami","fixed":["2.9.1"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":"pkg:bitnami/mlflow","source":"BIT-mlflow-2023-6568"},{"ecosystem":"PyPI","fixed":["2.9.0"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":null,"source":"GHSA-vwhf-3v6x-wff8"},{"ecosystem":"PyPI","fixed":["2.9.0"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":"pkg:pypi/mlflow","source":"GHSA-vwhf-3v6x-wff8"},{"ecosystem":"PyPI","fixed":["2.9.1"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":"pkg:pypi/mlflow","source":"PYSEC-2023-260"}],"prev":{"headline":"LearnPress \u003c= 4.2.5.7 - Unauthenticated SQL Injection via order_by","id":"CVE-2023-6567"},"products":["mlflow/mlflow"],"published":"2023-12-07","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-02","vendors":["mlflow"]},"summary":"Attackers can execute arbitrary JavaScript in victims' browsers by injecting malicious code into the Content-Type header of POST requests to MLflow.","url":"https://insights.sbomify.com/CVE-2023-6568/"}