Kritisch

Gradio Blocked Path ACL Bypass Vulnerability

  • Veröffentlicht: 14.01.2025
  • Aktualisiert: 11.10.2026 12:19

Summary

Gradio's Access Control List (ACL) for file paths can be bypassed by altering the letter case of a blocked file or directory path. This vulnerability arises due to the lack of case normalization in the file path validation logic. On case-insensitive file systems, such as those used by Windows and macOS, this flaw enables attackers to circumvent security restrictions and access sensitive files that should be protected.

This issue can lead to unauthorized data access, exposing sensitive information and undermining the integrity of Gradio's security model. Given Gradio's popularity for building web applications, particularly in machine learning and AI, this vulnerability may pose a substantial threat if exploited in production environments.

Affected Version

Gradio <= 5.6.0

Impact

  • Unauthorized Access: Sensitive files or directories specified in blocked_paths can be accessed by attackers.

  • Data Exposure: Critical files, such as configuration files or user data, may be leaked.

  • Security Breach: This can lead to broader application or system compromise if sensitive files contain credentials or API keys.

Root Cause

The blocked_paths parameter in Gradio block's initial configuration is designed to restrict user access to specific files or directories in the local file system. However, it does not account for case-insensitive operating systems, such as Windows and macOS. This oversight enables attackers to bypass ACL restrictions by changing the case of file paths.

Vulnerable snippet:

python
# https://github.com/gradio-app/gradio/blob/main/gradio/utils.py#L1500-L1517
def is_allowed_file(
    path: Path,
    blocked_paths: Sequence[str | Path],
    allowed_paths: Sequence[str | Path],
    created_paths: Sequence[str | Path],
) -> tuple[
    bool, Literal["in_blocklist", "allowed", "created", "not_created_or_allowed"]
]:
    in_blocklist = any(
        is_in_or_equal(path, blocked_path) for blocked_path in blocked_paths
    )
    if in_blocklist:
        return False, "in_blocklist"
    if any(is_in_or_equal(path, allowed_path) for allowed_path in allowed_paths):
        return True, "allowed"
    if any(is_in_or_equal(path, created_path) for created_path in created_paths):
        return True, "created"
    return False, "not_created_or_allowed"

Gradio relies on is_in_or_equal to determine if a file path is restricted. However, this logic fails to handle case variations in paths on case-insensitive file systems, leading to the bypass.

Proof of Concept (PoC)

Steps to Reproduce

  • Deploy a Gradio demo app on a case-insensitive operating system (e.g., Windows or macOS).

    bash
    import gradio as gr
    def update(name):
        return f"Welcome to Gradio, {name}!"
    
    with gr.Blocks() as demo:
        gr.Markdown("Start typing below and then click **Run** to see the output.")
        with gr.Row():
            inp = gr.Textbox(placeholder="What is your name?")
            out = gr.Textbox()
        btn = gr.Button("Run")
        btn.click(fn=update, inputs=inp, outputs=out)
    
    demo.launch(blocked_paths=['resources/admin'], allowed_paths=['resources/'])
  • Set up the file system:

    • Create a folder named resources in the same directory as the app, containing a file 1.txt.

    • Inside the resources folder, create a subfolder named admin containing a sensitive file credential.txt (this file should be inaccessible due to blocked_paths).

  • Perform the attack:

    • Access the sensitive file using a case-altered path:

      http://127.0.0.1:PORT/gradio_api/file=resources/adMin/credential.txt

Expected Result

Access to resources/admin/credential.txt should be blocked.

Actual Result

By altering the case in the path (e.g., adMin), the blocked ACL is bypassed, and unauthorized access to the sensitive file is granted.

image-20241119172439042

This demonstration highlights that flipping the case of restricted paths allows attackers to bypass Gradio's ACL and access sensitive data.

Remediation Recommendations

  1. Normalize Path Case:

    • Before evaluating paths against the ACL, normalize the case of both the requested path and the blocked paths (e.g., convert all paths to lowercase).

    • Example:

      python
      normalized_path = str(path).lower()
      normalized_blocked_paths = [str(p).lower() for p in blocked_paths]
  2. Update Documentation:

    • Warn developers about potential risks when deploying Gradio on case-insensitive file systems.
  3. Release Security Patches:

    • Notify users of the vulnerability and release an updated version of Gradio with the fixed logic.

Betroffene Software

Klicken Sie auf eine Technologie, um alle zugehörigen Schwachstellen anzuzeigen.

PlattformPaketAnfällige VersionenBehoben in
Python (PyPI) gradio < 5.11.0 5.11.0

Verweise

CVSS-Wert -
CVSS-Vektor
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Schwäche (CWE)
CWE-178, CWE-285
Plattform
Python (PyPI)
Paket
gradio
Veröffentlicht
14.01.2025
Aktualisiert
11.10.2026 12:19

Quellen und Lizenzen

OSV / GitHub Advisory Database - PYSEC-2025-118 - PyPA Advisory Database; CC BY 4.0

OSV / GitHub Advisory Database - GHSA-j2jg-fq62-7c3h - CC BY 4.0

Schwachstellenhistorie: gradio

Alle veröffentlichten Schwachstellen dieses Pakets (Python (PyPI)), neueste zuerst. Zeigt, ob es ein einmaliger Ausrutscher ist oder ein Paket, das man im Auge behalten muss.

Alle (51) im Archiv
Einträge insgesamt
51
Erste → letzte
12.2021 07.2026
Ohne Fix
13
In Angriffen ausgenutzt
0

Verteilung nach Schweregrad

  • Kritisch 5
  • Hoch 19
  • Mittel 22
  • Niedrig 5

Veröffentlichungen pro Jahr

  1. 2021: 1
  2. 2022: 1
  3. 2023: 5
  4. 2024: 28
  5. 2025: 9
  6. 2026: 7
Schweregrad:
  1. Hoch · 7.5 CVE-2024-8966 <= 5.22.0 keine Korrektur
  2. Hoch · 7.5 CVE-2024-10624 >= 4.38.0, <= 5.0.0-beta.2 keine Korrektur
  3. Hoch · 8.2 CVE-2024-10648 >= 4.0.0, <= 5.0.0b2 keine Korrektur
  4. Hoch · 7.5 CVE-2024-10569 >= 4.0.0, <= 5.0.0b2 keine Korrektur
  5. Gradio Blocked Path ACL Bypass Vulnerability dieser Eintrag
    Kritisch CVE-2025-23042 < 5.11.0 5.11.0
  6. Hoch · 7.5 CVE-2024-47867 < 5.0.0 5.0.0
  7. Hoch · 8.1 CVE-2024-1728 < 4.19.2 4.19.2
  8. Hoch · 8.6 CVE-2024-4325 <= 4.36.0 keine Korrektur
  9. Hoch · 7.5 CVE-2024-34510 < 4.20.0 4.20.0
  10. Hoch · 7.5 CVE-2024-1561 < 4.13.0 4.13.0
  11. Hoch · 7.3 CVE-2024-2206 < 4.18.0 4.18.0
  12. Kritisch · 8.3 CVE-2021-43831 < 2.5.0 2.5.0

Erkennen Sie Schwachstellen in Ihrer Anwendung

Mit der DockRay-Integration und aktivierter Softwareinventarisierung prüft DockRay gemeldete Komponentenversionen auf bekannte Schwachstellen und benachrichtigt Sie über bestätigte Treffer. Die Abdeckung hängt von der unterstützten Technologie und den verfügbaren Meldungen ab.

Anwendung verbinden
DockRay Newsletter

Anwendungssicherheit in Ihrem Postfach

Wichtige Schwachstellen, konkrete Empfehlungen und praktische Tipps für Ihre Anwendungen. Wählen Sie Ihre Technologien und verfolgen Sie, was für Ihr Projekt relevant ist.

  • Eine tägliche Zusammenfassung neuer Schwachstellen, auch kritischer.
  • Benachrichtigungen über wichtige Updates.
  • Praktische Tipps zur Sicherheit und Überwachung von Anwendungen.

Leer lassen, um Meldungen zu allen Technologien zu erhalten.

Kostenlos anmelden. In jeder E-Mail mit einem Klick abmelden.