{"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-47167 in the wild and no public exploit code.","fix":"Upgrade gradio to 5.0.0 or later.","what":"CVE-2024-47167 is a medium-severity server-side request forgery vulnerability in Gradio Project Gradio, published on 10 Oct 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-47167 and fix it if it is affected.\n\nWhat it is: CVE-2024-47167 is a medium-severity server-side request forgery vulnerability in Gradio Project Gradio, published on 10 Oct 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-47167 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- gradio (PyPI): affected all versions; fixed in 5.0.0\n- gradio (PyPI): affected all versions; fixed in 5.0.0\n- gradio (PyPI): affected all versions; fixed in 5.0.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-47167/ (Markdown: https://insights.sbomify.com/CVE-2024-47167/index.md)","id":"CVE-2024-47167","markdown":"https://insights.sbomify.com/CVE-2024-47167/index.md","name":"CVE-2024-47167","record":{"aliases":["GHSA-576c-3j53-r9jj","PYSEC-2024-215"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Python ML UI library","requires_auth":"none","summary":"Attackers can force Gradio servers to make internal HTTP requests and upload malicious files via URL inputs, risking data exfiltration and server compromise.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"gradio","vendor":"gradio_project"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Gradio is an open-source Python package designed for quick prototyping. This vulnerability relates to **Server-Side Request Forgery (SSRF)** in the `/queue/join` endpoint. Gradio’s `async_save_url_to_cache` function allows attackers to force the Gradio server to send HTTP requests to user-controlled URLs. This could enable attackers to target internal servers or services within a local network and possibly exfiltrate data or cause unwanted internal requests. Additionally, the content from these URLs is stored locally, making it easier for attackers to upload potentially malicious files to the server. This impacts users deploying Gradio servers that use components like the Video component which involve URL fetching. Users are advised to upgrade to `gradio\u003e=5` to address this issue.  As a workaround, users can disable or heavily restrict URL-based inputs in their Gradio applications to trusted domains only. Additionally, implementing stricter URL validation (such as allowinglist-based validation) and ensuring that local or internal network addresses cannot be requested via the `/queue/join` endpoint can help mitigate the risk of SSRF attacks.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":"2025-11-12","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-11-12T04:04:49Z","kind":"github_poc","ref":"https://github.com/alexan011/CVE-2024-47167-Environment-Setup","stars":0,"title":null}],"tier":"poc_unverified"},"has_fix":true,"headline":"SSRF in the path parameter of /queue/join in Gradio","id":"CVE-2024-47167","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":"gradio_project:gradio","products":["gradio_project:gradio"],"type":"ssrf","year":"2024"},"n_packages":3,"n_references":1,"next":{"headline":"The `enable_monitoring` flag set to `False` does not disable monitoring in Gradio","id":"CVE-2024-47168"},"packages":[{"ecosystem":"PyPI","fixed":["5.0.0"],"introduced":["0"],"last_affected":[],"package":"gradio","purl":null,"source":"GHSA-576c-3j53-r9jj"},{"ecosystem":"PyPI","fixed":["5.0.0"],"introduced":["0"],"last_affected":[],"package":"gradio","purl":"pkg:pypi/gradio","source":"GHSA-576c-3j53-r9jj"},{"ecosystem":"PyPI","fixed":["5.0.0"],"introduced":["0"],"last_affected":[],"package":"gradio","purl":"pkg:pypi/gradio","source":"PYSEC-2024-215"}],"prev":{"headline":"One-level read path traversal in `/custom_component` in Gradio","id":"CVE-2024-47166"},"products":["gradio"],"published":"2024-10-10","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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-10-11","vendors":["gradio-app"]},"summary":"Attackers can force Gradio servers to make internal HTTP requests and upload malicious files via URL inputs, risking data exfiltration and server compromise.","url":"https://insights.sbomify.com/CVE-2024-47167/"}