Skip to content

GHSA-hm3c-93pg-4cxw CVE-2024-47168 PYSEC-2024-198

In Gradio, the `enable_monitoring` flag set to `False` does not disable monitoring

Medium PyPI
Severity
0.0 / 10
Medium · CVSS 4.0
Exploit chance (EPSS)
0.33%
Chance of exploitation in the next 30 days. Higher than 26.41% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-670 Always-Incorrect Control Flow Implementation
Fix
4.44.0
Upgrade gradio to this version or later

Description

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

PyPI

PackageVulnerableFixed in
gradio
< 4.44.0
4.44.0

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

gradio PyPI → 4.44.0

pip
pip install --upgrade "gradio>=4.44.0"
poetry
poetry add "gradio>=4.44.0"
uv
uv add "gradio>=4.44.0"

Severity breakdown

CVSS 4.0 0.0

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

Attack vector
Network
Attack complexity
Low
Attack requirements
Present
Privileges required
Low
User interaction
None
Confidentiality (vulnerable system)
Low
Integrity (vulnerable system)
None
Availability (vulnerable system)
None
Confidentiality (subsequent systems)
None
Integrity (subsequent systems)
None
Availability (subsequent systems)
None

CVSS 3.1 4.3

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Weakness

CWE-670: Always-Incorrect Control Flow Implementation

The code contains a control flow path that does not reflect the algorithm that the path is intended to implement, leading to incorrect behavior any time this path is navigated.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-j36p-7w88-g82j
Gradio FileExplorer preprocess path traversal allows files outside root_dir to reach callbacks
High Also affects gradio
GHSA-6655-8ph2-63j3
Gradio: Audio cache key ignores metadata when saving numpy audio outputs
Low Also affects gradio
GHSA-7hp7-4p35-3cx2
Gradio contains a cookie injection vulnerability
Medium Also affects gradio
GHSA-jmh7-g254-2cq9
Gradio has SSRF via Malicious `proxy_url` Injection in `gr.load()` Config Processing
High Also affects gradio
GHSA-pfjf-5gxr-995x
Gradio has an Open Redirect in its OAuth Flow
Medium Also affects gradio
GHSA-39mp-8hj3-5c49
Gradio is Vulnerable to Absolute Path Traversal on Windows with Python 3.13+
High Also affects gradio
GHSA-h3h8-3v2v-rg7m
Gradio: Mocked OAuth Login Exposes Server Credentials and Uses Hardcoded Session Secret
Medium Also affects gradio
GHSA-8jw3-6x8j-v96g
Gradio Allows Unauthorized File Copy via Path Manipulation
High Also affects gradio
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor