gradio
Affected
- introduced
0, fixed4.44.0(ecosystem)
Fixed versions
4.44.0
Fix
- Fixed version
4.44.0pip install --upgrade gradio==4.44.0
Advisory
Also known as: CVE-2024-47869, PYSEC-2024-199
Gradio performs a non-constant-time comparison when comparing hashes
Impact
What kind of vulnerability is it? Who is impacted?
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.
Patches
Yes, please upgrade to gradio>4.44 to mitigate this issue.
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
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.
Medium Basis: The source's own band: MODERATE
0, fixed 4.44.0 (ecosystem)4.44.0
4.44.0pip install --upgrade gradio==4.44.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0