GHSA-rhq2-3vr9-6mcr
Vulnerability from github
Published
2022-01-21 23:43
Modified
2024-11-18 16:26
Severity ?
8.3 (High) - CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
9.3 (Critical) - CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N
9.3 (Critical) - CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N
Summary
Files on the host computer can be accessed from the Gradio interface
Details
Impact
This is a vulnerability that affects anyone who creates and publicly shares Gradio interfaces using gradio<2.4.8
. Because of the way that static files were being served, someone who generated a public Gradio link and shared it with others would potentially be exposing the files on the computer that generated the link, while the link was active. An attacker would be able to view the contents of a file on the computer if they knew the exact relative filepath. We do not have any evidence that this was ever exploited, but we treated the issue seriously and immediately took steps to mitigate it (see below)
Response
- We worked with @haby0 to immediately patch the issue and released a new version,
gradio 2.5.0
, within 24 hours of the issue being brought to our attention - We enabled a notification that is printed to anyone using an older version of gradio telling them to upgrade (see screenshot below)
- We expanded our test suite to test for this vulnerability ensuring that our patch does not get reverted in future releases of
gradio
Patches
The problem has been patched in gradio>=2.5.0
.
{ "affected": [ { "package": { "ecosystem": "PyPI", "name": "gradio" }, "ranges": [ { "events": [ { "introduced": "0" }, { "fixed": "2.5.0" } ], "type": "ECOSYSTEM" } ] } ], "aliases": [ "CVE-2021-43831" ], "database_specific": { "cwe_ids": [ "CWE-22" ], "github_reviewed": true, "github_reviewed_at": "2022-01-18T21:15:21Z", "nvd_published_at": "2021-12-15T20:15:00Z", "severity": "CRITICAL" }, "details": "### Impact\nThis is a vulnerability that affects anyone who creates and publicly shares Gradio interfaces using `gradio\u003c2.4.8`. Because of the way that static files were being served, someone who generated a public Gradio link and shared it with others would potentially be exposing the files on the computer that generated the link, while the link was active. An attacker would be able to view the contents of a file on the computer if they knew the exact relative filepath. We do not have any evidence that this was ever exploited, but we treated the issue seriously and immediately took steps to mitigate it (see below)\n\n### Response\n1. We worked with @haby0 to immediately patch the issue and released a new version, `gradio 2.5.0`, within 24 hours of the issue being brought to our attention \n2. We enabled a notification that is printed to anyone using an older version of gradio telling them to upgrade (see screenshot below)\n3. We expanded our test suite to test for this vulnerability ensuring that our patch does not get reverted in future releases of `gradio`\n\n\n\n### Patches\nThe problem has been patched in `gradio\u003e=2.5.0`.\n", "id": "GHSA-rhq2-3vr9-6mcr", "modified": "2024-11-18T16:26:18Z", "published": "2022-01-21T23:43:33Z", "references": [ { "type": "WEB", "url": "https://github.com/gradio-app/gradio/security/advisories/GHSA-rhq2-3vr9-6mcr" }, { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2021-43831" }, { "type": "WEB", "url": "https://github.com/gradio-app/gradio/commit/41bd3645bdb616e1248b2167ca83636a2653f781" }, { "type": "PACKAGE", "url": "https://github.com/gradio-app/gradio" }, { "type": "WEB", "url": "https://github.com/pypa/advisory-database/tree/main/vulns/gradio/PYSEC-2021-873.yaml" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L", "type": "CVSS_V3" }, { "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N", "type": "CVSS_V4" } ], "summary": "Files on the host computer can be accessed from the Gradio interface" }
Loading...
Loading...
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.