dbcve.org
GradioApplication · Gradio Project

CVE-2024-47167

CRITICAL · 9.8 CVSS v3.1 Published 2024-10-10
Fix available
A fix is available. Upgrade to 5.0.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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>=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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a Server-Side Request Forgery (SSRF) vulnerability in Gradio's `/queue/join` endpoint via the `async_save_url_to_cache` function. Attackers can supply malicious URLs that the Gradio server will fetch, enabling attacks against internal services and exfiltration of data from local network resources. The vulnerability specifically impacts components like Video that perform URL fetching.

MitigationUpgrade to Gradio version 5 or later to remediate this vulnerability. As a workaround, implement allowlist-based URL validation and block requests to internal/local network addresses.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GradioApplication
Affected:< 5.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Gradio version
    Run 'pip show gradio' or 'pip list | grep gradio' to see the installed version
    Affected if The version is lower than 5.0.0 (e.g., 4.x.x)
  2. Identify Gradio application entry points
    Search for Python files that import and run gradio (e.g., 'import gradio as gr' followed by 'app = gr.Block()' or 'demo.launch()'), or check for 'gradio' in requirements.txt or environment dependencies
    Affected if Gradio version < 5.0.0 is listed as a dependency or running in the environment
  3. Determine if Video or URL-fetching components are exposed
    Review Gradio application code for components that fetch from URLs (Video, File, Dataframe with file URLs, etc.) and check if they are mounted on a public or accessible endpoint
    Affected if Video or similar URL-fetching components are in use and accessible to untrusted users
  4. Assess network exposure of Gradio server
    Check how the Gradio app was launched (e.g., 'demo.launch(server_name="0.0.0.0")' makes it externally accessible; 'server_name="127.0.0.1"' limits to localhost)
    Affected if The server is bound to 0.0.0.0 or a public IP and the /queue/join endpoint is reachable

You are affected if Gradio version < 5.0.0 is running and the /queue/join endpoint with URL-fetching components like Video is accessible to untrusted users on a network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.0.0 or later
Fixed in 5.0.0
Interim mitigation

Upgrade to Gradio version 5 or later to remediate this vulnerability. As a workaround, implement allowlist-based URL validation and block requests to internal/local network addresses.

Recommended fix High confidence

gradio>=5.0.0

  1. Check current installed version: pip show gradio | grep Version
  2. Upgrade Gradio to version 5.0.0 or later: pip install --upgrade gradio>=5.0.0
  3. Verify the upgrade was successful: pip show gradio | grep Version
  4. If using a requirements.txt file, update the Gradio version entry to gradio>=5.0.0 and run pip install -r requirements.txt
  5. Test your application to ensure functionality remains intact after the upgrade
Caveat Major version upgrade from 4.x to 5.x may include breaking changes; review Gradio 5.0 release notes for API changes and migrate any incompatible code

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gradio Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47167 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-47167 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data