{"answers":{"affected":"3 open source packages ship an affected version, including gradio. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-47869 in the wild and no public exploit code.","fix":"Upgrade gradio to 4.44.0 or later.","what":"CVE-2024-47869 is a low-severity vulnerability in Gradio Project Gradio, published on 10 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-47869 and fix it if it is affected.\n\nWhat it is: CVE-2024-47869 is a low-severity vulnerability in Gradio Project Gradio, published on 10 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-47869 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- gradio (PyPI): affected all versions; fixed in 4.44.0\n- gradio (PyPI): affected all versions; fixed in 4.44.0\n- gradio (PyPI): affected all versions; fixed in 4.44.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-47869/ (Markdown: https://insights.sbomify.com/CVE-2024-47869/index.md)","id":"CVE-2024-47869","markdown":"https://insights.sbomify.com/CVE-2024-47869/index.md","name":"CVE-2024-47869","record":{"aliases":["GHSA-j757-pf57-f8r4","PYSEC-2024-199"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Python web UI library","requires_auth":"low_privilege","summary":"Timing attack in Gradio allows attackers to bypass authentication and access the analytics dashboard by inferring hashes via response time analysis.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"gradio","vendor":"gradio_project"}],"cvss":{"score":2.3,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-203","name":"Observable Discrepancy"}],"description":"Gradio is an open-source Python package designed for quick prototyping. This vulnerability involves a **timing attack** in the way Gradio compares hashes for the `analytics_dashboard` function. Since the comparison is not done in constant time, an attacker could exploit this by measuring the response time of different requests to infer the correct hash byte-by-byte. This can lead to unauthorized access to the analytics dashboard, especially if the attacker can repeatedly query the system with different keys. Users are advised to upgrade to `gradio\u003e4.44` to mitigate this issue. To mitigate the risk before applying the patch, developers can manually patch the `analytics_dashboard` dashboard to use a **constant-time comparison** function for comparing sensitive values, such as hashes. Alternatively, access to the analytics dashboard can be disabled.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Non-constant-time comparison when comparing hashes in Gradio","id":"CVE-2024-47869","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":"gradio_project:gradio","products":["gradio_project:gradio"],"type":"security_feature_bypass","year":"2024"},"n_packages":3,"n_references":1,"next":{"headline":"Race condition in update_root_in_config may redirect user traffic in Gradio","id":"CVE-2024-47870"},"packages":[{"ecosystem":"PyPI","fixed":["4.44.0"],"introduced":["0"],"last_affected":[],"package":"gradio","purl":null,"source":"GHSA-j757-pf57-f8r4"},{"ecosystem":"PyPI","fixed":["4.44.0"],"introduced":["0"],"last_affected":[],"package":"gradio","purl":"pkg:pypi/gradio","source":"GHSA-j757-pf57-f8r4"},{"ecosystem":"PyPI","fixed":["4.44.0"],"introduced":["0"],"last_affected":[],"package":"gradio","purl":"pkg:pypi/gradio","source":"PYSEC-2024-199"}],"prev":{"headline":"Several components’ post-process steps may allow arbitrary file leaks in Gradio","id":"CVE-2024-47868"},"products":["gradio"],"published":"2024-10-10","related":[{"cvss_score":9.8,"headline":"Withdrawn Advisory: Gradio was discovered to contain a code injection vulnerability via the component /gradio/component_meta.py","id":"CVE-2024-39236","kev_date_added":null,"published":"2024-07-01"},{"cvss_score":9.6,"headline":"Command Injection in gradio-app/gradio","id":"CVE-2023-6572","kev_date_added":null,"published":"2023-12-14"},{"cvss_score":8.8,"headline":"Improper Neutralization of Formula Elements in a CSV File in Gradio Flagging","id":"CVE-2022-24770","kev_date_added":null,"published":"2022-03-17"},{"cvss_score":8.7,"headline":"Gradio \u003c 6.16.0 Path Traversal via FileExplorer.preprocess()","id":"CVE-2026-49119","kev_date_added":null,"published":"2026-07-01"},{"cvss_score":8.7,"headline":"Gradio Blocked Path ACL Bypass Vulnerability","id":"CVE-2025-23042","kev_date_added":null,"published":"2025-01-14"},{"cvss_score":8.6,"headline":"Server-Side Request Forgery (SSRF) in gradio-app/gradio","id":"CVE-2024-4325","kev_date_added":null,"published":"2024-06-06"},{"cvss_score":8.6,"headline":"Command Injection in gradio-app/gradio via deploy+test-visual.yml workflow","id":"CVE-2024-1540","kev_date_added":null,"published":"2024-03-27"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-10-11","vendors":["gradio-app"]},"summary":"Timing attack in Gradio allows attackers to bypass authentication and access the analytics dashboard by inferring hashes via response time analysis.","url":"https://insights.sbomify.com/CVE-2024-47869/"}