How many CVEs have patched setAcceptParamNames?

3 published CVEs changed setAcceptParamNames in apache/struts, in 3 distinct patches totalling 15 changed lines, between 2012 and 2012.

What is the latest CVE that changed setAcceptParamNames?

CVE-2012-4387 (Denial of service in Apache Struts), published 2012-09-05, changed lines 159 to 168 of xwork-core/src/main/java/com/opensymphony/xwork2/interceptor/ParametersInterceptor.java.

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

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

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

Security data

Weaknesses (CWE)The MITRE CWE weakness catalog
Attack Patterns (CAPEC)MITRE CAPEC attack patterns
CNAsNumbering authorities and report cards
VendorsVulnerabilities by vendor
Patched FunctionsWhere CVE fixes land in code

Tools

CVSS CalculatorScore CVSS 4.0, 3.1, 3.0 & 2.0
Badge BuilderEmbeddable SVG badges for READMEs

Resources

LearnSecurity guides
Data SourcesCVE data sources

About Blog Pricing Demo

Home
Patched Functions
Apache
Struts
SetAcceptParamNames

RadicalNotion.AI

We do not sell or share your personal information.

Security Data

CWE Directory
CAPEC Directory
CNA Directory
CNA Leaderboard
CNA Report Cards
Vendor Directory
Patched Functions
Data Sources

Calculators

CVSS Calculator
CVSS 4.0
CVSS 3.1
CVSS 3.0
CVSS 2.0
Badge Builder

Platform

My Vulnerabilities
Insights
Notifications
Pricing

Learn

Guides
What is a CVE?
What is CVSS?
The CISA KEV catalog
What is EPSS?

Company

About
Blog
Careers
Contact
Demo

Account

Legal

Security
Privacy
Terms

RadicalNotion.AI

Security data

Weaknesses (CWE)The MITRE CWE weakness catalog
Attack Patterns (CAPEC)MITRE CAPEC attack patterns
CNAsNumbering authorities and report cards
VendorsVulnerabilities by vendor
Patched FunctionsWhere CVE fixes land in code

Tools

CVSS CalculatorScore CVSS 4.0, 3.1, 3.0 & 2.0
Badge BuilderEmbeddable SVG badges for READMEs

Resources

LearnSecurity guides
Data SourcesCVE data sources

About Blog Pricing Demo

Home
Patched Functions
Apache
Struts
SetAcceptParamNames

setAcceptParamNames in apache/struts: Patched by 3 CVEs

apache/struts

Function

setAcceptParamNames

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

xwork-core/src/main/java/com/opensymphony/xwork2/interceptor/ParametersInterceptor.java

Last patched September 5, 2012

CVEs

That changed this function

Distinct patches

Backports counted once

Lines changed

Added plus removed

2012

Years

By CVE publication date

Overview

setAcceptParamNames in apache/struts was changed by 3 published CVE fixes in 2012, in 3 distinct patches that added or removed 15 lines in total.

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

CVEs that patched it

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

Denial of service in Apache Struts
CVE-2012-4387 · lines 159–168 · +10 −1
Medium · CVSS 5.0
EPSS 8.1%2012-09-05
Apache Struts's ParameterInterceptor component does not prevent access to public constructors
CVE-2012-0393 · line 154 · +1 −1
Medium · CVSS 6.4
EPSS 36.3%2012-01-08
Apache Struts's DebuggingInterceptor component allows remote code execution in developer mode
CVE-2012-0394 · line 154 · +1 −1
Medium · CVSS 6.8
EPSS 72.9%2012-01-08

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.

1setExcludeParamsxwork-core/src/main/java/com/opensymphony/xwork2/interceptor/ParametersInterceptor.java3 CVEs · 2 patches2012 to 2014
2asCollectionxwork-core/src/main/java/com/opensymphony/xwork2/interceptor/ParametersInterceptor.java2 CVEs · 1 patches2012
3isAcceptedxwork-core/src/main/java/com/opensymphony/xwork2/interceptor/ParametersInterceptor.java1 CVEs · 2 patches2012
4setParamNameMaxLengthxwork-core/src/main/java/com/opensymphony/xwork2/interceptor/ParametersInterceptor.java1 CVEs · 2 patches2012
5initializeHardCodedExcludePatternsxwork-core/src/main/java/com/opensymphony/xwork2/interceptor/ParametersInterceptor.java1 CVEs · 1 patches2014
6ParametersInterceptorxwork-core/src/main/java/com/opensymphony/xwork2/interceptor/ParametersInterceptor.java1 CVEs · 1 patches2014

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 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 getFile2 CVEs · core/src/main/java/org/apache/struts2/dispatcher/multipart/JakartaMultiPartRequest.java

All patched functions in apache/struts

Frequently asked questions

Common questions about CVE fixes to setAcceptParamNames.

How many CVEs have patched setAcceptParamNames?: 3 published CVEs changed setAcceptParamNames in apache/struts, in 3 distinct patches totalling 15 changed lines, between 2012 and 2012.
What is the latest CVE that changed setAcceptParamNames?: CVE-2012-4387 (Denial of service in Apache Struts), published 2012-09-05, changed lines 159 to 168 of xwork-core/src/main/java/com/opensymphony/xwork2/interceptor/ParametersInterceptor.java.
How does setAcceptParamNames compare to the rest of apache/struts?: apache/struts has 40 CVEs with a located fix in total; 3 of them changed setAcceptParamNames.
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

xwork-core/src/main/java/com/opensymphony/xwork2/interceptor/ParametersInterceptor.java on GitHub (opens in a new tab)
All patched functions in apache/struts
Patched functions directory

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

On this page

Overview
CVEs that patched it
Other functions in these files
Other hotspots in the repository
FAQ
References