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

THẤP 3.7CVE-2024-47869 · GHSA-j757-pf57-f8r4 · PYSEC-2024-199 · Công bố 10/10/2024 · cập nhật 17/06/2026

Tóm tắt nhanh

CVE-2024-47869 là lỗ hổng mức THẤP (CVSS 3.7) ảnh hưởng gradio, gradio (gradio project).
Xác suất bị khai thác trong 30 ngày tới (EPSS): 0.29%, cao hơn 22.1% các lỗ hổng khác.
Cách xử lý: cập nhật lên 4.44.0 hoặc mới hơn.

Gói / sản phẩm	Phiên bản bị ảnh hưởng	Phiên bản đã vá
gradio PyPI	`< 4.44.0`	`4.44.0`
gradio gradio_project	`< 4.44.0`	`4.44.0`

Mô tả

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.

Mô tả của NVD

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.