How many CVEs have patched __init__?

5 published CVEs changed __init__ in gradio-app/gradio, in 10 distinct patches totalling 59 changed lines, between 2023 and 2024.

What is the latest CVE that changed __init__?

CVE-2024-47164 (Gradio's `is_in_or_equal` function may be bypassed), published 2024-10-10, changed lines 418 of gradio/blocks.py.

How does __init__ compare to the rest of gradio-app/gradio?

gradio-app/gradio has 24 CVEs with a located fix in total; 5 of them changed __init__.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

gradio-app/gradio

Function

6 files

init

Name: __init__ in gradio-app/gradio: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

Defined in 6 files

Last patched October 10, 2024

5

CVEs

That changed this function

10

Distinct patches

Backports counted once

59

Lines changed

Added plus removed

2023–2024

Years

By CVE publication date

Overview

__init__ in gradio-app/gradio was changed by 5 published CVE fixes between 2023 and 2024, in 10 distinct patches that added or removed 59 lines in total.

The name occurs in 6 files: gradio/blocks.py, client/python/gradio_client/client.py, gradio/components/base.py, gradio/queueing.py, gradio/routes.py, gradio/components/file_explorer.py.

gradio-app/gradio has 24 CVEs with a located fix in total, so 21% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed __init__, newest first, with the lines each fix touched.

Gradio's `is_in_or_equal` function may be bypassed
CVE-2024-47164 · gradio/blocks.py · line 418 · +1 −1
Medium · CVSS 6.9
EPSS 0.7%2024-10-10
Gradio's `is_in_or_equal` function may be bypassed
CVE-2024-47164 · gradio/components/base.py · line 231 · +1 −1
Medium · CVSS 6.9
EPSS 0.7%2024-10-10
Gradio's `is_in_or_equal` function may be bypassed
CVE-2024-47164 · gradio/components/file_explorer.py · line 89 · +1 −1
Medium · CVSS 6.9
EPSS 0.7%2024-10-10
Local File Inclusion in gradio-app/gradio
CVE-2024-1728 · gradio/blocks.py · line 122 · +1 −6
Critical · CVSS 9.2
EPSS 85.4%2024-04-10
Local File Inclusion in gradio-app/gradio
CVE-2024-1728 · gradio/routes.py · line 136 · +1 −3
Critical · CVSS 9.2
EPSS 85.4%2024-04-10
gradio Server-Side Request Forgery vulnerability
CVE-2024-2206 · gradio/components/base.py · lines 198–203 · +6 −1
Medium · CVSS 6.5
EPSS 0.4%2024-03-27
LFI in Gradio
CVE-2024-0964 · client/python/gradio_client/client.py · lines 128–906 · +20 −10 in 3 hunks
Critical · CVSS 9.4
EPSS 1.0%2024-02-05
LFI in Gradio
CVE-2024-0964 · gradio/queueing.py · lines 40–63 · +3 −1 in 2 hunks
Critical · CVSS 9.4
EPSS 1.0%2024-02-05
Gradio vulnerable to arbitrary file read and proxying of arbitrary URLs
CVE-2023-34239 · gradio/blocks.py · line 741 · +1 −0
Medium · CVSS 6.9
EPSS 0.7%2023-06-07

Get an alert when the next CVE fix lands in gradio-app/gradio, with the patched functions.

Monitor gradio CVEs

Other functions in these files

Functions in the same files that CVE fixes also changed.

Other hotspots in the repository

Functions in gradio-app/gradio changed by the most CVE fixes.

file5 CVEs · gradio/routes.py build_proxy_request3 CVEs · gradio/routes.py is_in_or_equal3 CVEs · gradio/utils.py _move_to_cache3 CVEs · gradio/processing_utils.py reverse_proxy2 CVEs · gradio/routes.py get_block_instance2 CVEs · gradio/blocks.py

All patched functions in gradio-app/gradio

Frequently asked questions

Common questions about CVE fixes to __init__.

How many CVEs have patched __init__?: 5 published CVEs changed __init__ in gradio-app/gradio, in 10 distinct patches totalling 59 changed lines, between 2023 and 2024.
What is the latest CVE that changed __init__?: CVE-2024-47164 (Gradio's `is_in_or_equal` function may be bypassed), published 2024-10-10, changed lines 418 of gradio/blocks.py.
How does __init__ compare to the rest of gradio-app/gradio?: gradio-app/gradio has 24 CVEs with a located fix in total; 5 of them changed __init__.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track gradio-app/gradio CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing