ghsa-77xq-6g77-h274
Vulnerability from github
6.9 (Medium) - CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
Impact
What kind of vulnerability is it? Who is impacted?
This vulnerability relates to the bypass of directory traversal checks within the is_in_or_equal
function. This function, intended to check if a file resides within a given directory, can be bypassed with certain payloads that manipulate file paths using ..
(parent directory) sequences. Attackers could potentially access restricted files if they are able to exploit this flaw, although the difficulty is high. This primarily impacts users relying on Gradio’s blocklist or directory access validation, particularly when handling file uploads.
Patches
Yes, please upgrade to gradio>=5.0
to address this issue.
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
As a workaround, users can manually sanitize and normalize file paths in their Gradio deployment before passing them to the is_in_or_equal
function. Ensuring that all file paths are properly resolved and absolute can help mitigate the bypass vulnerabilities caused by the improper handling of ..
sequences or malformed paths.
{ "affected": [ { "package": { "ecosystem": "PyPI", "name": "gradio" }, "ranges": [ { "events": [ { "introduced": "0" }, { "fixed": "5.0.0" } ], "type": "ECOSYSTEM" } ] } ], "aliases": [ "CVE-2024-47164" ], "database_specific": { "cwe_ids": [ "CWE-22" ], "github_reviewed": true, "github_reviewed_at": "2024-10-10T21:27:47Z", "nvd_published_at": "2024-10-10T22:15:10Z", "severity": "MODERATE" }, "details": "### Impact\n**What kind of vulnerability is it? Who is impacted?**\n\nThis vulnerability relates to the **bypass of directory traversal checks** within the `is_in_or_equal` function. This function, intended to check if a file resides within a given directory, can be bypassed with certain payloads that manipulate file paths using `..` (parent directory) sequences. Attackers could potentially access restricted files if they are able to exploit this flaw, although the difficulty is high. This primarily impacts users relying on Gradio\u2019s blocklist or directory access validation, particularly when handling file uploads.\n\n### Patches\nYes, please upgrade to `gradio\u003e=5.0` 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 manually sanitize and normalize file paths in their Gradio deployment before passing them to the `is_in_or_equal` function. Ensuring that all file paths are properly resolved and absolute can help mitigate the bypass vulnerabilities caused by the improper handling of `..` sequences or malformed paths.", "id": "GHSA-77xq-6g77-h274", "modified": "2025-01-21T17:53:30Z", "published": "2024-10-10T21:27:47Z", "references": [ { "type": "WEB", "url": "https://github.com/gradio-app/gradio/security/advisories/GHSA-77xq-6g77-h274" }, { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47164" }, { "type": "WEB", "url": "https://github.com/gradio-app/gradio/commit/08b51590163b306fd874f543f6fcaf23ac7d2646" }, { "type": "PACKAGE", "url": "https://github.com/gradio-app/gradio" }, { "type": "WEB", "url": "https://github.com/pypa/advisory-database/tree/main/vulns/gradio/PYSEC-2024-213.yaml" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N", "type": "CVSS_V3" }, { "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N", "type": "CVSS_V4" } ], "summary": "Gradio\u0027s `is_in_or_equal` function may be bypassed" }
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- 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.