cve.bz

CVE-2024-47168 gradio project gradio

2.3 lowEPSS 0.3%Fix available

Low (2.3) in gradio project gradio. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in gradio 4.44.0.

On this page
Gradio is an open-source Python package designed for quick prototyping. This vulnerability involves data exposure due to the enable_monitoring flag not properly disabling monitoring when set to False. Even when monitoring is supposedly disabled, an attacker or unauthorized user can still access the monitoring dashboard by directly requesting the /monitoring endpoint. This means that sensitive application analytics may still be exposed, particularly in environments where monitoring is expected to be disabled. Users who set enable_monitoring=False to prevent unauthorized access to monitoring data are impacted. Users are advised to upgrade to gradio>=4.44 to address this issue. There are no known workarounds for this vulnerability.

Severity

CVSS 4.0

2.3 low
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

CVSS 3.1

4.3 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 27th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2024-10-11. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-670 Always-Incorrect Control Flow Implementation
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

  • gradio (PyPI): fixed in 4.44.0

Ask an AI about this CVE

Show the promptExplain CVE-2024-47168 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-47168?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-47168?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-47168 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
gradio_project:gradiobefore 4.44.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-hm3c-93pg-4cxwPyPIgradio<4.44.04.44.0
PYSEC-2024-198PyPIgradio<4.44.04.44.0

References

Check your stackJSON