Non-constant-time comparison when comparing hashes in Gradio
Description
Gradio is an open-source Python package designed for quick prototyping. This vulnerability involves a timing attack in the way Gradio compares hashes for the analytics_dashboard function. Since the comparison is not done in constant time, an attacker could exploit this by measuring the response time of different requests to infer the correct hash byte-by-byte. This can lead to unauthorized access to the analytics dashboard, especially if the attacker can repeatedly query the system with different keys. Users are advised to upgrade to gradio>4.44 to mitigate this issue. To mitigate the risk before applying the patch, developers can manually patch the analytics_dashboard dashboard to use a constant-time comparison function for comparing sensitive values, such as hashes. Alternatively, access to the analytics dashboard can be disabled.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
gradioPyPI | < 4.44.0 | 4.44.0 |
Affected products
2- Range: < 4.44
Patches
Vulnerability mechanics
References
4- github.com/advisories/GHSA-j757-pf57-f8r4ghsaADVISORY
- nvd.nist.gov/vuln/detail/CVE-2024-47869ghsaADVISORY
- github.com/gradio-app/gradio/security/advisories/GHSA-j757-pf57-f8r4ghsax_refsource_CONFIRMWEB
- github.com/pypa/advisory-database/tree/main/vulns/gradio/PYSEC-2024-199.yamlghsaWEB
News mentions
0No linked articles in our index yet.