GHSA-4Q3C-CJ7G-JCWF

Vulnerability from github – Published: 2024-10-10 22:03 – Updated: 2025-01-21 17:18
VLAI?
Summary
Gradio has several components with post-process steps allow arbitrary file leaks
Details

Impact

What kind of vulnerability is it? Who is impacted?

This is a data validation vulnerability affecting several Gradio components, which allows arbitrary file leaks through the post-processing step. Attackers can exploit these components by crafting requests that bypass expected input constraints. This issue could lead to sensitive files being exposed to unauthorized users, especially when combined with other vulnerabilities, such as issue TOB-GRADIO-15. The components most at risk are those that return or handle file data.

Vulnerable Components:

  1. String to FileData: DownloadButton, Audio, ImageEditor, Video, Model3D, File, UploadButton.
  2. Complex data to FileData: Chatbot, MultimodalTextbox.
  3. Direct file read in preprocess: Code.
  4. Dictionary converted to FileData: ParamViewer, Dataset.

Exploit Scenarios:

  1. A developer creates a Dropdown list that passes values to a DownloadButton. An attacker bypasses the allowed inputs, sends an arbitrary file path (like /etc/passwd), and downloads sensitive files.
  2. An attacker crafts a malicious payload in a ParamViewer component, leaking sensitive files from a server through the arbitrary file leak.

Patches

Yes, the issue has been resolved in gradio>5.0. Upgrading to the latest version will mitigate this vulnerability.

Severity ?
5.3 (Medium)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
6.9 (Medium)
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Show details on source website
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "gradio"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.0.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2024-47868"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-200",
      "CWE-22"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2024-10-10T22:03:03Z",
    "nvd_published_at": "2024-10-10T23:15:02Z",
    "severity": "MODERATE"
  },
  "details": "### Impact\n**What kind of vulnerability is it? Who is impacted?**\n\nThis is a **data validation vulnerability** affecting several Gradio components, which allows arbitrary file leaks through the post-processing step. Attackers can exploit these components by crafting requests that bypass expected input constraints. This issue could lead to sensitive files being exposed to unauthorized users, especially when combined with other vulnerabilities, such as issue TOB-GRADIO-15. The components most at risk are those that return or handle file data.\n\n### Vulnerable Components:\n1. **String to FileData:** DownloadButton, Audio, ImageEditor, Video, Model3D, File, UploadButton.\n2. **Complex data to FileData:** Chatbot, MultimodalTextbox.\n3. **Direct file read in preprocess:** Code.\n4. **Dictionary converted to FileData:** ParamViewer, Dataset.\n\n### Exploit Scenarios:\n1. A developer creates a Dropdown list that passes values to a DownloadButton. An attacker bypasses the allowed inputs, sends an arbitrary file path (like `/etc/passwd`), and downloads sensitive files.\n2. An attacker crafts a malicious payload in a ParamViewer component, leaking sensitive files from a server through the arbitrary file leak.\n\n### Patches\nYes, the issue has been resolved in `gradio\u003e5.0`. Upgrading to the latest version will mitigate this vulnerability.\n",
  "id": "GHSA-4q3c-cj7g-jcwf",
  "modified": "2025-01-21T17:18:26Z",
  "published": "2024-10-10T22:03:03Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/gradio-app/gradio/security/advisories/GHSA-4q3c-cj7g-jcwf"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47868"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/gradio-app/gradio"
    },
    {
      "type": "WEB",
      "url": "https://github.com/pypa/advisory-database/tree/main/vulns/gradio/PYSEC-2024-217.yaml"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
      "type": "CVSS_V3"
    },
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "Gradio has several components with post-process steps allow arbitrary file leaks"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.