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-47166, PYSEC-2024-197
Gradio has a one-level read path traversal in /custom_component
Impact
What kind of vulnerability is it? Who is impacted?
This vulnerability involves a one-level read path traversal in the /custom_component endpoint. Attackers can exploit this flaw to access and leak source code from custom Gradio components by manipulating the file path in the request. Although the traversal is limited to a single directory level, it could expose proprietary or sensitive code that developers intended to keep private. This impacts users who have developed custom Gradio components and are hosting them on publicly accessible servers.
Patches
Yes, please upgrade to gradio>=4.44 to address this issue.
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
As a workaround, developers can sanitize the file paths and ensure that components are not stored in publicly accessible directories.
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