INCIDENT MAP

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

Gradio's CORS origin validation accepts the null origin

CVE-2024-47165 ยท 2024-10-10 moderate

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

How it works, in short

The localhost origin list includes the null origin, so sandboxed iframes can make cross-origin requests and read the responses. (Our summary, written by a model. The source text is below.)

Details

Impact

What kind of vulnerability is it? Who is impacted?

This vulnerability relates to CORS origin validation accepting a null origin. When a Gradio server is deployed locally, the localhost_aliases variable includes "null" as a valid origin. This allows attackers to make unauthorized requests from sandboxed iframes or other sources with a null origin, potentially leading to data theft, such as user authentication tokens or uploaded files. This impacts users running Gradio locally, especially those using basic authentication.

Patches

Yes, please upgrade to gradio>=5.0 to address this issue.

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

As a workaround, users can manually modify the localhost_aliases list in their local Gradio deployment to exclude "null" as a valid origin. By removing this value, the Gradio server will no longer accept requests from sandboxed iframes or sources with a null origin, mitigating the potential for exploitation.

References

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