INCIDENT MAP

Browse / AI Framework and Platform Flaws / CVE-2024-47869

Gradio performs a non-constant-time comparison when comparing hashes

CVE-2024-47869 ยท 2024-10-10 moderate

Class
AI Framework and Platform Flaws (filed by a model that read the advisory)
Technique
Authentication and access control
Affected
gradio (PyPI)
CVSS
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
0.3% chance of exploitation in 30 days

How it works, in short

The analytics dashboard compares secret hashes in non-constant time, so response timing lets an attacker recover the hash byte by byte. (Our summary, written by a model. The source text is below.)

Details

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.

References

Source: GitHub Advisory Database, used under CC BY 4.0.