How many CVEs have patched custom_component_path?

1 published CVEs changed custom_component_path in gradio-app/gradio, in 1 distinct patches totalling 12 changed lines, between 2024 and 2024.

What is the latest CVE that changed custom_component_path?

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

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

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

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

custom_component_path

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

gradio/routes.py

Last patched October 10, 2024

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

12

Lines changed

Added plus removed

2024

Years

By CVE publication date

Overview

custom_component_path in gradio-app/gradio was changed by 1 published CVE fixes in 2024, in 1 distinct patches that added or removed 12 lines in total.

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

CVEs that patched it

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

Gradio's `is_in_or_equal` function may be bypassed
CVE-2024-47164 · lines 473–491 · +8 −4 in 2 hunks
Medium · CVSS 6.9
EPSS 0.7%2024-10-10

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 file 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 __init__3 CVEs · gradio/blocks.py _move_to_cache3 CVEs · gradio/processing_utils.py reverse_proxy2 CVEs · gradio/routes.py

All patched functions in gradio-app/gradio

Frequently asked questions

Common questions about CVE fixes to custom_component_path.

How many CVEs have patched custom_component_path?: 1 published CVEs changed custom_component_path in gradio-app/gradio, in 1 distinct patches totalling 12 changed lines, between 2024 and 2024.
What is the latest CVE that changed custom_component_path?: CVE-2024-47164 (Gradio's `is_in_or_equal` function may be bypassed), published 2024-10-10, changed lines 473 to 491 of gradio/routes.py.
How does custom_component_path compare to the rest of gradio-app/gradio?: gradio-app/gradio has 24 CVEs with a located fix in total; 1 of them changed custom_component_path.
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