AI agent vulnerability · Gradio

CVE-2024-47168: In Gradio, the `enable_monitoring` flag set to `False` does not disable monitoring

lowCVSS 4.0 2.3 · 3.1 4.3GHSA-hm3c-93pg-4cxw

Impact What kind of vulnerability is it? Who is impacted? This vulnerability involves data exposure due to the enablemonitoring 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.

Published Oct 10, 2024 · Updated Jan 21, 2025

Affected packages

gradio

Ecosystem: PyPI
Affected: < 4.44.0
Fixed in: 4.44.0
Check: pip show gradio

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Impact

What kind of vulnerability is it? Who is impacted?

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.

Patches

Yes, please upgrade to gradio>=4.44 to address this issue.

Credited to ahpaleus, Vasco-jofra.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More Gradio vulnerabilities

All Gradio entries