Gradio vulnerable to arbitrary file read and proxying of arbitrary URLs
CVE-2023-34239 · GHSA-3qqg-pgqq-3695 · published 2023-06-09 · updated 2024-09-20
- Severity
- Medium
- CVSS score
- 7.3
- Chance of exploitation (EPSS)
- 0.65%
- Fixed in
- 3.34.0
- Exploitation No known exploitation
- Automatable Yes
- Technical impact Total
- CISA SSVC
There are two separate security vulnerabilities here: (1) a security vulnerability that allows users to read arbitrary files on the machines that are running shared Gradio apps (2) the ability of users to use machines that are sharing Gradio apps to proxy arbitrary URLs
Upgrade gradio to 3.34.0 or later.
Both problems have been solved, please upgrade gradio to 3.34.0 or higher
Not possible to workaround except by taking down any shared Gradio apps
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| gradio | PyPI | < 3.34.0 | 3.34.0 |
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLangflow affected by Remote Code Execution via validate_code() exec()langflowExploited
- CriticalJupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routesjupyter-mcp-server
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
- CriticalGradio Blocked Path ACL Bypass Vulnerabilitygradio
- CriticalGradio allows users to access arbitrary filesgradio
- CriticalGradio Exposure of Sensitive Information to an Unauthorized Actor vulnerabilitygradio
- CriticalFiles on the host computer can be accessed from the Gradio interfacegradio
- HighGradio FileExplorer preprocess path traversal allows files outside root_dir to reach callbacksgradio
- HighGradio contains a cookie injection vulnerabilitygradio
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.