CVSS: 2.3EPSS: 0%CPEs: 1EXPL: 0CVE-2024-47166 – One-level read path traversal in `/custom_component` in Gradio
https://notcve.org/view.php?id=CVE-2024-47166
Gradio is an open-source Python package designed for quick prototyping. 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. • https://github.com/gradio-app/gradio/security/advisories/GHSA-37qc-qgx6-9xjv • CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') •
CVSS: 6.9EPSS: 0%CPEs: 1EXPL: 0CVE-2024-47167 – SSRF in the path parameter of /queue/join in Gradio
https://notcve.org/view.php?id=CVE-2024-47167
Gradio is an open-source Python package designed for quick prototyping. This vulnerability relates to **Server-Side Request Forgery (SSRF)** in the `/queue/join` endpoint. Gradio’s `async_save_url_to_cache` function allows attackers to force the Gradio server to send HTTP requests to user-controlled URLs. This could enable attackers to target internal servers or services within a local network and possibly exfiltrate data or cause unwanted internal requests. Additionally, the content from these URLs is stored locally, making it easier for attackers to upload potentially malicious files to the server. • https://github.com/gradio-app/gradio/security/advisories/GHSA-576c-3j53-r9jj • CWE-918: Server-Side Request Forgery (SSRF) •
CVSS: 2.3EPSS: 0%CPEs: 1EXPL: 0CVE-2024-47168 – The `enable_monitoring` flag set to `False` does not disable monitoring in Gradio
https://notcve.org/view.php?id=CVE-2024-47168
Gradio is an open-source Python package designed for quick prototyping. This vulnerability involves data exposure due to the enable_monitoring flag not properly disabling monitoring when set to False. Even when monitoring is supposedly disabled, an attacker or unauthorized user can still access the monitoring dashboard by directly requesting the /monitoring endpoint. This means that sensitive application analytics may still be exposed, particularly in environments where monitoring is expected to be disabled. Users who set enable_monitoring=False to prevent unauthorized access to monitoring data are impacted. • https://github.com/gradio-app/gradio/security/advisories/GHSA-hm3c-93pg-4cxw • CWE-670: Always-Incorrect Control Flow Implementation •