How many CVEs have patched getFileNames?

1 published CVEs changed getFileNames in apache/struts, in 2 distinct patches totalling 2 changed lines, between 2023 and 2023.

What is the latest CVE that changed getFileNames?

CVE-2023-41835 (Apache Struts Improper Control of Dynamically-Managed Code Resources vulnerability), published 2023-12-05, changed lines 271 of core/src/main/java/org/apache/struts2/dispatcher/multipart/JakartaMultiPartRequest.java.

How does getFileNames compare to the rest of apache/struts?

apache/struts has 40 CVEs with a located fix in total; 1 of them changed getFileNames.

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

apache/struts

Function

getFileNames

Name: getFileNames in apache/struts: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

core/src/main/java/org/apache/struts2/dispatcher/multipart/JakartaMultiPartRequest.java

Last patched December 5, 2023

1

CVEs

That changed this function

2

Distinct patches

Backports counted once

2

Lines changed

Added plus removed

2023

Years

By CVE publication date

Overview

getFileNames in apache/struts was changed by 1 published CVE fixes in 2023, in 2 distinct patches that added or removed 2 lines in total.

apache/struts has 40 CVEs with a located fix in total, so 3% of them touched this function.

CVEs that patched it

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

Apache Struts Improper Control of Dynamically-Managed Code Resources vulnerability
CVE-2023-41835 · line 271 · +1 −1
High · CVSS 7.5
EPSS 7.3%2023-12-05

Get an alert when the next CVE fix lands in apache/struts, with the patched functions.

Monitor struts CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in apache/struts changed by the most CVE fixes.

execute5 CVEs · core/src/main/java/org/apache/struts2/dispatcher/mapper/DefaultActionMapper.java cleanupActionName4 CVEs · core/src/main/java/org/apache/struts2/dispatcher/mapper/DefaultActionMapper.java processNormalFormField3 CVEs · core/src/main/java/org/apache/struts2/dispatcher/multipart/JakartaMultiPartRequest.java setAcceptParamNames3 CVEs · xwork-core/src/main/java/com/opensymphony/xwork2/interceptor/ParametersInterceptor.java intercept3 CVEs · core/src/main/java/org/apache/struts2/interceptor/CookieInterceptor.java setExcludeParams3 CVEs · xwork-core/src/main/java/com/opensymphony/xwork2/interceptor/ParametersInterceptor.java

All patched functions in apache/struts

Frequently asked questions

Common questions about CVE fixes to getFileNames.

How many CVEs have patched getFileNames?: 1 published CVEs changed getFileNames in apache/struts, in 2 distinct patches totalling 2 changed lines, between 2023 and 2023.
What is the latest CVE that changed getFileNames?: CVE-2023-41835 (Apache Struts Improper Control of Dynamically-Managed Code Resources vulnerability), published 2023-12-05, changed lines 271 of core/src/main/java/org/apache/struts2/dispatcher/multipart/JakartaMultiPartRequest.java.
How does getFileNames compare to the rest of apache/struts?: apache/struts has 40 CVEs with a located fix in total; 1 of them changed getFileNames.
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 apache/struts 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