How many CVEs have patched _move_to_cache?

3 published CVEs changed _move_to_cache in gradio-app/gradio, in 3 distinct patches totalling 22 changed lines, between 2024 and 2024.

What is the latest CVE that changed _move_to_cache?

CVE-2024-4941 (Local File Inclusion in JSON component in gradio-app/gradio), published 2024-06-06, changed lines 493 of gradio/processing_utils.py.

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

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

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

_move_to_cache

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

gradio/processing_utils.py

Last patched June 6, 2024

3

CVEs

That changed this function

3

Distinct patches

Backports counted once

22

Lines changed

Added plus removed

2024

Years

By CVE publication date

Overview

_move_to_cache in gradio-app/gradio was changed by 3 published CVE fixes in 2024, in 3 distinct patches that added or removed 22 lines in total.

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

CVEs that patched it

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

Local File Inclusion in JSON component in gradio-app/gradio
CVE-2024-4941 · line 493 · +0 −1
High · CVSS 7.5
EPSS 0.8%2024-06-06
Local File Inclusion in gradio-app/gradio
CVE-2024-1728 · lines 270–277 · +8 −0
Critical · CVSS 9.2
EPSS 85.4%2024-04-10
gradio Server-Side Request Forgery vulnerability
CVE-2024-2206 · lines 269–281 · +13 −0
Medium · CVSS 6.5
EPSS 0.4%2024-03-27

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 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 _move_to_cache.

How many CVEs have patched _move_to_cache?: 3 published CVEs changed _move_to_cache in gradio-app/gradio, in 3 distinct patches totalling 22 changed lines, between 2024 and 2024.
What is the latest CVE that changed _move_to_cache?: CVE-2024-4941 (Local File Inclusion in JSON component in gradio-app/gradio), published 2024-06-06, changed lines 493 of gradio/processing_utils.py.
How does _move_to_cache compare to the rest of gradio-app/gradio?: gradio-app/gradio has 24 CVEs with a located fix in total; 3 of them changed _move_to_cache.
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