diff --git a/advisories/github-reviewed/2024/10/GHSA-576c-3j53-r9jj/GHSA-576c-3j53-r9jj.json b/advisories/github-reviewed/2024/10/GHSA-576c-3j53-r9jj/GHSA-576c-3j53-r9jj.json new file mode 100644 index 00000000000..a061b54be08 --- /dev/null +++ b/advisories/github-reviewed/2024/10/GHSA-576c-3j53-r9jj/GHSA-576c-3j53-r9jj.json @@ -0,0 +1,61 @@ +{ + "schema_version": "1.4.0", + "id": "GHSA-576c-3j53-r9jj", + "modified": "2024-10-10T22:02:36Z", + "published": "2024-10-10T22:01:44Z", + "aliases": [ + "CVE-2024-47167" + ], + "summary": "Gradio vulnerable to SSRF in the path parameter of /queue/join", + "details": "### Impact \n**What kind of vulnerability is it? Who is impacted?**\n\nThis 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. This impacts users deploying Gradio servers that use components like the Video component which involve URL fetching.\n\n### Patches \nYes, please upgrade to `gradio>=5` to address this issue.\n\n### Workarounds \n**Is there a way for users to fix or remediate the vulnerability without upgrading?**\n\nAs a workaround, users can disable or heavily restrict URL-based inputs in their Gradio applications to trusted domains only. Additionally, implementing stricter URL validation (such as allowinglist-based validation) and ensuring that local or internal network addresses cannot be requested via the `/queue/join` endpoint can help mitigate the risk of SSRF attacks.", + "severity": [ + { + "type": "CVSS_V3", + "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N" + }, + { + "type": "CVSS_V4", + "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N" + } + ], + "affected": [ + { + "package": { + "ecosystem": "PyPI", + "name": "gradio" + }, + "ranges": [ + { + "type": "ECOSYSTEM", + "events": [ + { + "introduced": "0" + }, + { + "fixed": "5.0.0" + } + ] + } + ] + } + ], + "references": [ + { + "type": "WEB", + "url": "https://github.com/gradio-app/gradio/security/advisories/GHSA-576c-3j53-r9jj" + }, + { + "type": "PACKAGE", + "url": "https://github.com/gradio-app/gradio" + } + ], + "database_specific": { + "cwe_ids": [ + "CWE-918" + ], + "severity": "MODERATE", + "github_reviewed": true, + "github_reviewed_at": "2024-10-10T22:01:44Z", + "nvd_published_at": null + } +} \ No newline at end of file diff --git a/advisories/github-reviewed/2024/10/GHSA-8c87-gvhj-xm8m/GHSA-8c87-gvhj-xm8m.json b/advisories/github-reviewed/2024/10/GHSA-8c87-gvhj-xm8m/GHSA-8c87-gvhj-xm8m.json new file mode 100644 index 00000000000..0c4ae1398f7 --- /dev/null +++ b/advisories/github-reviewed/2024/10/GHSA-8c87-gvhj-xm8m/GHSA-8c87-gvhj-xm8m.json @@ -0,0 +1,61 @@ +{ + "schema_version": "1.4.0", + "id": "GHSA-8c87-gvhj-xm8m", + "modified": "2024-10-10T22:02:52Z", + "published": "2024-10-10T22:02:52Z", + "aliases": [ + "CVE-2024-47867" + ], + "summary": "Gradio lacks integrity checking on the downloaded FRP client", + "details": "### Impact\nThis vulnerability is a **lack of integrity check** on the downloaded FRP client, which could potentially allow attackers to introduce malicious code. If an attacker gains access to the remote URL from which the FRP client is downloaded, they could modify the binary without detection, as the Gradio server does not verify the file's checksum or signature. \n\n**Who is impacted?** \nAny users utilizing the Gradio server's sharing mechanism that downloads the FRP client could be affected by this vulnerability, especially those relying on the executable binary for secure data tunneling.\n\n### Patches\nYes, please upgrade to `gradio>=5.0`, which includes a fix to verify the integrity of the downloaded binary.\n\n### Workarounds\nThere is no direct workaround for this issue without upgrading. However, users can manually validate the integrity of the downloaded FRP client by implementing checksum or signature verification in their own environment to ensure the binary hasn't been tampered with.", + "severity": [ + { + "type": "CVSS_V3", + "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H" + }, + { + "type": "CVSS_V4", + "score": "CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N" + } + ], + "affected": [ + { + "package": { + "ecosystem": "PyPI", + "name": "gradio" + }, + "ranges": [ + { + "type": "ECOSYSTEM", + "events": [ + { + "introduced": "0" + }, + { + "fixed": "5.0.0" + } + ] + } + ] + } + ], + "references": [ + { + "type": "WEB", + "url": "https://github.com/gradio-app/gradio/security/advisories/GHSA-8c87-gvhj-xm8m" + }, + { + "type": "PACKAGE", + "url": "https://github.com/gradio-app/gradio" + } + ], + "database_specific": { + "cwe_ids": [ + "CWE-494" + ], + "severity": "HIGH", + "github_reviewed": true, + "github_reviewed_at": "2024-10-10T22:02:52Z", + "nvd_published_at": null + } +} \ No newline at end of file diff --git a/advisories/github-reviewed/2024/10/GHSA-hm3c-93pg-4cxw/GHSA-hm3c-93pg-4cxw.json b/advisories/github-reviewed/2024/10/GHSA-hm3c-93pg-4cxw/GHSA-hm3c-93pg-4cxw.json new file mode 100644 index 00000000000..8610be4a992 --- /dev/null +++ b/advisories/github-reviewed/2024/10/GHSA-hm3c-93pg-4cxw/GHSA-hm3c-93pg-4cxw.json @@ -0,0 +1,61 @@ +{ + "schema_version": "1.4.0", + "id": "GHSA-hm3c-93pg-4cxw", + "modified": "2024-10-10T22:02:30Z", + "published": "2024-10-10T22:02:30Z", + "aliases": [ + "CVE-2024-47168" + ], + "summary": "In Gradio, the `enable_monitoring` flag set to `False` does not disable monitoring", + "details": "### Impact\nWhat kind of vulnerability is it? Who is impacted?\n\nThis 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.\n\n### Patches\nYes, please upgrade to gradio>=4.44 to address this issue.\n\n", + "severity": [ + { + "type": "CVSS_V3", + "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N" + }, + { + "type": "CVSS_V4", + "score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N" + } + ], + "affected": [ + { + "package": { + "ecosystem": "PyPI", + "name": "gradio" + }, + "ranges": [ + { + "type": "ECOSYSTEM", + "events": [ + { + "introduced": "0" + }, + { + "fixed": "4.44.0" + } + ] + } + ] + } + ], + "references": [ + { + "type": "WEB", + "url": "https://github.com/gradio-app/gradio/security/advisories/GHSA-hm3c-93pg-4cxw" + }, + { + "type": "PACKAGE", + "url": "https://github.com/gradio-app/gradio" + } + ], + "database_specific": { + "cwe_ids": [ + "CWE-670" + ], + "severity": "LOW", + "github_reviewed": true, + "github_reviewed_at": "2024-10-10T22:02:30Z", + "nvd_published_at": null + } +} \ No newline at end of file