{"answers":{"affected":"3 open source packages ship an affected version, including gradio. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-34510 in the wild and no public exploit code.","fix":"Upgrade gradio to 4.20.0 or later.","what":"CVE-2024-34510 is a high-severity vulnerability in Gradio Project Gradio, published on 5 May 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-34510 and fix it if it is affected.\n\nWhat it is: CVE-2024-34510 is a high-severity vulnerability in Gradio Project Gradio, published on 5 May 2024. 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-2024-34510 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- gradio (PyPI): affected all versions; fixed in 4.20.0\n- gradio (PyPI): affected all versions; fixed in 4.20.0\n- gradio (PyPI): affected all versions; fixed in 4.20.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-34510/ (Markdown: https://insights.sbomify.com/CVE-2024-34510/index.md)","id":"CVE-2024-34510","markdown":"https://insights.sbomify.com/CVE-2024-34510/index.md","name":"CVE-2024-34510","record":{"aliases":["GHSA-rvfh-h6c7-fc3c","PYSEC-2024-255"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Gradio Python library","requires_auth":"none","summary":"An attacker can leak credentials from Gradio applications running on Windows due to improper output neutralization.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"gradio","vendor":"gradio_project"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AC:L/AV:N/A:N/C:H/I:N/PR:N/S:U/UI:N","version":"3.1"},"cwes":[{"id":"CWE-116","name":"Improper Encoding or Escaping of Output"}],"description":"Gradio before 4.20 allows credential leakage on Windows.","ecosystems":["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":"Gradio allows credential leakage on Windows","id":"CVE-2024-34510","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":"gradio_project:gradio","products":["gradio_project:gradio"],"type":"information_disclosure","year":"2024"},"n_packages":3,"n_references":2,"next":{"headline":"image-optimizer allows PHAR deserialization","id":"CVE-2024-34515"},"packages":[{"ecosystem":"PyPI","fixed":["4.20.0"],"introduced":["0"],"last_affected":[],"package":"gradio","purl":null,"source":"GHSA-rvfh-h6c7-fc3c"},{"ecosystem":"PyPI","fixed":["4.20.0"],"introduced":["0"],"last_affected":[],"package":"gradio","purl":"pkg:pypi/gradio","source":"GHSA-rvfh-h6c7-fc3c"},{"ecosystem":"PyPI","fixed":["4.20.0"],"introduced":["0"],"last_affected":[],"package":"gradio","purl":"pkg:pypi/gradio","source":"PYSEC-2024-255"}],"prev":{"headline":"Null dereference in n/a","id":"CVE-2024-34509"},"products":["n/a"],"published":"2024-05-05","related":[{"cvss_score":9.8,"headline":"Withdrawn Advisory: Gradio was discovered to contain a code injection vulnerability via the component /gradio/component_meta.py","id":"CVE-2024-39236","kev_date_added":null,"published":"2024-07-01"},{"cvss_score":9.6,"headline":"Command Injection in gradio-app/gradio","id":"CVE-2023-6572","kev_date_added":null,"published":"2023-12-14"},{"cvss_score":8.8,"headline":"Improper Neutralization of Formula Elements in a CSV File in Gradio Flagging","id":"CVE-2022-24770","kev_date_added":null,"published":"2022-03-17"},{"cvss_score":8.7,"headline":"Gradio \u003c 6.16.0 Path Traversal via FileExplorer.preprocess()","id":"CVE-2026-49119","kev_date_added":null,"published":"2026-07-01"},{"cvss_score":8.7,"headline":"Gradio Blocked Path ACL Bypass Vulnerability","id":"CVE-2025-23042","kev_date_added":null,"published":"2025-01-14"},{"cvss_score":8.6,"headline":"Server-Side Request Forgery (SSRF) in gradio-app/gradio","id":"CVE-2024-4325","kev_date_added":null,"published":"2024-06-06"},{"cvss_score":8.6,"headline":"Command Injection in gradio-app/gradio via deploy+test-visual.yml workflow","id":"CVE-2024-1540","kev_date_added":null,"published":"2024-03-27"}],"sources":[{"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":"partial"},"state":"PUBLISHED","updated":"2024-11-19","vendors":["n/a"]},"summary":"An attacker can leak credentials from Gradio applications running on Windows due to improper output neutralization.","url":"https://insights.sbomify.com/CVE-2024-34510/"}