CVE-2023-51449High· 8.6▾ MidnightPoC availableGradio makes the `/file` secure against file traversal and server-side request forgery attacks
▾ Midnight zone — Critical, or high with PoC / in-the-wild
impact 47.3 · likelihood 5.7 · exploitation 12
A public proof-of-concept already exists for this vulnerability — see Exploit availability below.
Public exploit / PoC code seen in 1 source. Availability, not in-the-wild use.
Exploit-prediction probability, daily snapshots since Sep 12.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
28%
Nuclei ×1 (last check)
Older versions of gradio contained a vulnerability in the /file route which made them susceptible to file traversal attacks in which an attacker could access arbitrary files on a machine running a Gradio app with a public URL (e.g. if the demo was created with share=True, or on Hugging Face Spaces) if they knew the path of files to look for.
This was not possible through regular URLs passed into a browser, but it was possible through the use of programmatic tools such as curl with the --pass-as-is flag.
Furthermore, the /file route in Gradio apps also contained a vulnerability that made it possible to use it for SSRF attacks.
Both of these vulnerabilities have been fixed in gradio==4.11.0
gradio < 4.11.0Upgrade to a patched release:
gradio 4.11.0Connected by shared product, vendor, weakness, or advisory.
CVE-2024-1183Medium· 6.5gradio Server-Side Request Forgery vulnerability
CVE-2023-6572Critical· 9.6Gradio Exposure of Sensitive Information to an Unauthorized Actor vulnerability
CVE-2021-43831High· 8.3Files on the host computer can be accessed from the Gradio interface
CVE-2024-1561High· 7.5gradio vulnerable to Path Traversal
CVE-2024-4940Medium· 5.4Open redirect in gradio
CVE-2024-4325High· 8.6Server-Side Request Forgery in gradio