In Gradio, the `enable_monitoring` flag set to `False` does not disable monitoring
Low4.3CVE-2024-47168 · Published Oct 10, 2024 · updated Jan 21, 2025
### 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.
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| gradio PyPI | < 4.44.0 | 4.44.0 |
Details and references
- CVSS 3.1
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
- Severity from
- GitHub (reviewed advisory)
- Weakness
- CWE-670
- Also known as
- CVE-2024-47168, PYSEC-2024-198
More Gradio advisories
All Gradio| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| Oct 102024 | Gradio's dropdown component pre-process step does not limit the values to those in the dropdown list | Low5.3 | 5.0.0 |
| Oct 102024 | Gradio has an XSS on every Gradio server via upload of HTML files, JS files, or SVG files | Medium5.4 | 5.0.0 |
| Oct 102024 | Gradio uses insecure communication between the FRP client and server | High8.1 | 5.0.0 |
| Oct 102024 | Gradio has a race condition in update_root_in_config may redirect user traffic | High7.0 | 5.0.0 |
| Oct 102024 | Gradio performs a non-constant-time comparison when comparing hashes | Medium3.7 | 4.44.0 |
| Oct 102024 | Gradio has several components with post-process steps allow arbitrary file leaks | Medium5.3 | 5.0.0 |