dbcve.org
GradioApplication · Gradio Project

CVE-2024-47867

HIGH · 7.5 CVSS v3.1 Published 2024-10-10
Fix available
A fix is available. Upgrade to 5.0.0 or later.
See remediation →
84/100
Remediation priority · High
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 is a **lack of integrity check** on the downloaded FRP client, which could potentially allow attackers to introduce malicious code. If an attacker gains access to the remote URL from which the FRP client is downloaded, they could modify the binary without detection, as the Gradio server does not verify the file's checksum or signature. Any users utilizing the Gradio server's sharing mechanism that downloads the FRP client could be affected by this vulnerability, especially those relying on the executable binary for secure data tunneling. There is no direct workaround for this issue without upgrading. However, users can manually validate the integrity of the downloaded FRP client by implementing checksum or signature verification in their own environment to ensure the binary hasn't been tampered with.

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

Gradio downloads an FRP client binary for its sharing mechanism without verifying the file's checksum or signature. If an attacker compromises the remote download URL, they can replace the binary with malicious code, which will then execute on user systems using Gradio's sharing feature.

MitigationUpgrade Gradio to a version that implements integrity verification (checksum or signature validation) for the FRP client download. Until then, manually verify any downloaded FRP binaries against known-good checksums.

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
None
Integrity
High
Availability
None

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

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 number
    Affected if Version is lower than 5.0.0 (e.g., 4.x.x, 3.x.x)
  2. Determine if sharing feature is in use
    Look for 'share=True' in Gradio app initialization code, or check if 'share' parameter was passed when launching the Gradio interface
    Affected if Sharing is enabled (share=True) or has been used recently
  3. Locate downloaded FRP client binary
    Search for 'frp' binary files in Gradio's cache or data directories: find ~/.cache -name '*frp*' 2>/dev/null and check the gradio working directory
    Affected if FRP binary files exist on the system, indicating prior sharing feature use
  4. Inspect network activity during sharing
    Monitor network connections when launching Gradio with share=True; check if Gradio attempts to download from remote URLs without integrity verification
    Affected if Downloads occur without checksum or signature validation

You are affected if Gradio version is below 5.0.0 and the sharing feature (share=True) has been enabled or used, as this triggers the insecure FRP binary download.

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 Gradio to a version that implements integrity verification (checksum or signature validation) for the FRP client download. Until then, manually verify any downloaded FRP binaries against known-good checksums.

Recommended fix High confidence

Gradio 5.0.0

  1. Run `pip install --upgrade gradio` to upgrade to the latest version
  2. Verify the installation by running `gradio --version` and confirm it shows version 5.0.0 or later
  3. If using a virtual environment, ensure the environment is activated before upgrading
  4. After upgrading, test the sharing mechanism to ensure FRP client downloads correctly

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

Fix this in Gradio Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47867 — 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-47867 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