# CVE-2024-1729: Timing Attack Vulnerability in gradio-app/gradio

> Attackers can bypass authentication in Gradio by exploiting timing differences in password validation to guess credentials and gain unauthorized access.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/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:** Not needed
- **Fix available:** Yes
- **Published:** 29 Mar 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-hmx6-r76c-85g9, PYSEC-2026-1416

## What is CVE-2024-1729?

CVE-2024-1729 is a medium-severity authentication bypass vulnerability in Gradio Project Gradio, published on 29 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A timing attack vulnerability exists in the gradio-app/gradio repository, specifically within the login function in routes.py. The vulnerability arises from the use of a direct comparison operation (`app.auth[username] == password`) to validate user credentials, which can be exploited to guess passwords based on response times. Successful exploitation of this vulnerability could allow an attacker to bypass authentication mechanisms and gain unauthorized access.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

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

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


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

Products: Gradio Project Gradio.

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

Upgrade gradio to 4.19.2 or later.

## Is CVE-2024-1729 being exploited?

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

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

What it is: CVE-2024-1729 is a medium-severity authentication bypass vulnerability in Gradio Project Gradio, published on 29 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-1729 exists.

Affected packages and fixed versions:
- gradio (PyPI): affected all versions; fixed in 4.19.2
- gradio (PyPI): affected all versions; fixed in 4.19.2
- gradio (PyPI): affected all versions; fixed in 4.19.2

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-1729/ (Markdown: https://insights.sbomify.com/CVE-2024-1729/index.md)
```

## Sources

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

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