Skip to content

Gradio apps vulnerable to timing attacks to guess password

Moderate severity GitHub Reviewed Published Feb 22, 2024 in gradio-app/gradio • Updated Apr 8, 2024

Package

pip gradio (pip)

Affected versions

< 4.19.2

Patched versions

4.19.2

Description

Impact

This security policy is with regards to a timing attack that allows users of Gradio apps to potentially guess the password of password-protected Gradio apps. This relies on the fact that string comparisons in Python terminate early, as soon as there is a string mismatch. Because Gradio apps are, by default, not rate-limited, a user could brute-force millions of guesses to figure out the correct username and password.

Patches

Yes, the problem has been patched in Gradio version 4.19.2 or higher. We have no knowledge of this exploit being used against users of Gradio applications, but we encourage all users to upgrade to Gradio 4.19.2 or higher.

Fixed in: gradio-app/gradio@e329f1f

References

@abidlabs abidlabs published to gradio-app/gradio Feb 22, 2024
Published to the GitHub Advisory Database Feb 22, 2024
Reviewed Feb 22, 2024
Published by the National Vulnerability Database Mar 29, 2024
Last updated Apr 8, 2024

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.043%
(10th percentile)

Weaknesses

CVE ID

CVE-2024-1729

GHSA ID

GHSA-hmx6-r76c-85g9

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.