# CVE-2024-47868: Several components’ post-process steps may allow arbitrary file leaks in Gradio > Attackers can exploit Gradio components to leak arbitrary files from the server by bypassing input validation in post-processing steps. - **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 10 Oct 2024 - **Updated:** 11 Oct 2024 - **Also known as:** GHSA-4q3c-cj7g-jcwf, PYSEC-2024-217 ## What is CVE-2024-47868? CVE-2024-47868 is a medium-severity path traversal 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. ### Official description Gradio is an open-source Python package designed for quick prototyping. This is a **data validation vulnerability** affecting several Gradio components, which allows arbitrary file leaks through the post-processing step. Attackers can exploit these components by crafting requests that bypass expected input constraints. This issue could lead to sensitive files being exposed to unauthorized users, especially when combined with other vulnerabilities, such as issue TOB-GRADIO-15. The components most at risk are those that return or handle file data. Vulnerable Components: 1. **String to FileData:** DownloadButton, Audio, ImageEditor, Video, Model3D, File, UploadButton. 2. **Complex data to FileData:** Chatbot, MultimodalTextbox. 3. **Direct file read in preprocess:** Code. 4. **Dictionary converted to FileData:** ParamViewer, Dataset. Exploit Scenarios: 1. A developer creates a Dropdown list that passes values to a DownloadButton. An attacker bypasses the allowed inputs, sends an arbitrary file path (like `/etc/passwd`), and downloads sensitive files. 2. An attacker crafts a malicious payload in a ParamViewer component, leaking sensitive files from a server through the arbitrary file leak. This issue has been resolved in `gradio>5.0`. Upgrading to the latest version will mitigate this vulnerability. There are no known workarounds for this vulnerability. Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2024-47868? 3 open source packages ship an affected version, including gradio. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `gradio` | PyPI | All versions | 5.0.0 | | `gradio` | PyPI | All versions | 5.0.0 | | `gradio` | PyPI | All versions | 5.0.0 | Products: Gradio Project Gradio. ## How do I fix CVE-2024-47868? Upgrade gradio to 5.0.0 or later. ## Is CVE-2024-47868 being exploited? There is no known exploitation of CVE-2024-47868 in the wild and no public exploit code. ## Other vulnerabilities in Gradio Project Gradio - [CVE-2024-39236](https://insights.sbomify.com/CVE-2024-39236/): Withdrawn Advisory: Gradio was discovered to contain a code injection vulnerability via the component /gradio/component_meta.py (critical 9.8) - [CVE-2023-6572](https://insights.sbomify.com/CVE-2023-6572/): Command Injection in gradio-app/gradio (critical 9.6) - [CVE-2022-24770](https://insights.sbomify.com/CVE-2022-24770/): Improper Neutralization of Formula Elements in a CSV File in Gradio Flagging (high 8.8) - [CVE-2026-49119](https://insights.sbomify.com/CVE-2026-49119/): Gradio < 6.16.0 Path Traversal via FileExplorer.preprocess() (high 8.7) - [CVE-2025-23042](https://insights.sbomify.com/CVE-2025-23042/): Gradio Blocked Path ACL Bypass Vulnerability (high 8.7) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-47868 and fix it if it is affected. What it is: CVE-2024-47868 is a medium-severity path traversal 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. Exploitation: There is no known exploitation of CVE-2024-47868 in the wild and no public exploit code. Affected packages and fixed versions: - gradio (PyPI): affected all versions; fixed in 5.0.0 - gradio (PyPI): affected all versions; fixed in 5.0.0 - gradio (PyPI): affected all versions; fixed in 5.0.0 Task: 1. 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. 2. 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. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-47868/ (Markdown: https://insights.sbomify.com/CVE-2024-47868/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-47868 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-47868 - OSV: https://osv.dev/vulnerability/CVE-2024-47868 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-47868/ Summaries are generated and may contain mistakes; the official description above is the record.