INCIDENT MAP

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

Gradio has several components with post-process steps allow arbitrary file leaks

CVE-2024-47868 ยท 2024-10-10 moderate

Class
AI Framework and Platform Flaws (filed by a model that read the advisory)
Technique
Path traversal and file access
Also involves
Sensitive Data Disclosure
Affected
gradio (PyPI)
Gets past
Input filter or sanitiser
CVSS
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
0.8% chance of exploitation in 30 days

How it works, in short

Gradio file components accept arbitrary file paths from requests that bypass intended input constraints, so the server returns sensitive local files. (Our summary, written by a model. The source text is below.)

Details

Impact

What kind of vulnerability is it? Who is impacted?

This is a data validation vulnerability affecting several Gradio components, which allows arbitrary file leaks through the post-processing step. Attackers can exploit these components by crafting requests that bypass expected input constraints. This issue could lead to sensitive files being exposed to unauthorized users, especially when combined with other vulnerabilities, such as issue TOB-GRADIO-15. The components most at risk are those that return or handle file data.

Vulnerable Components:

1. String to FileData: DownloadButton, Audio, ImageEditor, Video, Model3D, File, UploadButton. 2. Complex data to FileData: Chatbot, MultimodalTextbox. 3. Direct file read in preprocess: Code. 4. Dictionary converted to FileData: ParamViewer, Dataset.

Exploit Scenarios:

1. A developer creates a Dropdown list that passes values to a DownloadButton. An attacker bypasses the allowed inputs, sends an arbitrary file path (like /etc/passwd), and downloads sensitive files. 2. An attacker crafts a malicious payload in a ParamViewer component, leaking sensitive files from a server through the arbitrary file leak.

Patches

Yes, the issue has been resolved in gradio>5.0. Upgrading to the latest version will mitigate this vulnerability.

References

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