# CVE-2024-1183: SSRF Vulnerability in gradio-app/gradio

> Attackers can exploit an SSRF flaw in Gradio to scan internal network ports by manipulating the file parameter in GET requests.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 16 Apr 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-qh6x-j82h-vpf9, PYSEC-2026-1419

## What is CVE-2024-1183?

CVE-2024-1183 is a medium-severity server-side request forgery vulnerability in Gradio Project Gradio, published on 16 Apr 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An SSRF (Server-Side Request Forgery) vulnerability exists in the gradio-app/gradio repository, allowing attackers to scan and identify open ports within an internal network. By manipulating the 'file' parameter in a GET request, an attacker can discern the status of internal ports based on the presence of a 'Location' header or a 'File not allowed' error in the response.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2024-1183?

3 open source packages ship an affected version, including gradio. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gradio` | PyPI | All versions | 4.10.0 |
| `gradio` | PyPI | All versions | 4.10.0 |
| `gradio` | PyPI | All versions | 4.10.0 |

Products: Gradio Project Gradio.

## How do I fix CVE-2024-1183?

Upgrade gradio to 4.10.0 or later.

## Is CVE-2024-1183 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-1183 exists.

Public exploit code:

- Gradio - Server Side Request Forgery (nuclei): http/cves/2024/CVE-2024-1183.yaml

## 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-1183 and fix it if it is affected.

What it is: CVE-2024-1183 is a medium-severity server-side request forgery vulnerability in Gradio Project Gradio, published on 16 Apr 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-1183 exists.

Affected packages and fixed versions:
- gradio (PyPI): affected all versions; fixed in 4.10.0
- gradio (PyPI): affected all versions; fixed in 4.10.0
- gradio (PyPI): affected all versions; fixed in 4.10.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-1183/ (Markdown: https://insights.sbomify.com/CVE-2024-1183/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-1183
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-1183
- OSV: https://osv.dev/vulnerability/CVE-2024-1183

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-1183/
Summaries are generated and may contain mistakes; the official description above is the record.