How many CVEs have patched StandardContext?

2 published CVEs changed StandardContext in apache/tomcat, in 4 distinct patches totalling 13 changed lines, between 2011 and 2014.

What is the latest CVE that changed StandardContext?

CVE-2013-4590 (Exposure of Sensitive Information to an Unauthorized Actor in Apache Tomcat), published 2014-02-26, changed lines 701 to 707 of java/org/apache/catalina/core/StandardContext.java.

How does StandardContext compare to the rest of apache/tomcat?

apache/tomcat has 135 CVEs with a located fix in total; 2 of them changed StandardContext.

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/tomcat

Function

StandardContext

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

java/org/apache/catalina/core/StandardContext.java

Last patched February 26, 2014

2

CVEs

That changed this function

4

Distinct patches

Backports counted once

13

Lines changed

Added plus removed

2011–2014

Years

By CVE publication date

Overview

StandardContext in apache/tomcat was changed by 2 published CVE fixes between 2011 and 2014, in 4 distinct patches that added or removed 13 lines in total.

apache/tomcat has 135 CVEs with a located fix in total, so 1% of them touched this function.

CVEs that patched it

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

Exposure of Sensitive Information to an Unauthorized Actor in Apache Tomcat
CVE-2013-4590 · lines 701–707 · +7 −0
Medium · CVSS 4.3
EPSS 9.5%2014-02-26
Apache Tomcat allows remote attackers to bypass intended access restrictions
CVE-2011-1088 · lines 840–845 · +6 −0
Medium · CVSS 5.8
EPSS 6.5%2011-03-14

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

Monitor tomcat CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

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

fixDocBase5 CVEs · java/org/apache/catalina/startup/ContextConfig.java expand5 CVEs · java/org/apache/catalina/startup/ExpandWar.java validate5 CVEs · java/org/apache/catalina/startup/ExpandWar.java invoke4 CVEs · java/org/apache/catalina/authenticator/AuthenticatorBase.java parseParts4 CVEs · java/org/apache/catalina/connector/Request.java parseChunkHeader4 CVEs · java/org/apache/coyote/http11/filters/ChunkedInputFilter.java

All patched functions in apache/tomcat

Frequently asked questions

Common questions about CVE fixes to StandardContext.

How many CVEs have patched StandardContext?: 2 published CVEs changed StandardContext in apache/tomcat, in 4 distinct patches totalling 13 changed lines, between 2011 and 2014.
What is the latest CVE that changed StandardContext?: CVE-2013-4590 (Exposure of Sensitive Information to an Unauthorized Actor in Apache Tomcat), published 2014-02-26, changed lines 701 to 707 of java/org/apache/catalina/core/StandardContext.java.
How does StandardContext compare to the rest of apache/tomcat?: apache/tomcat has 135 CVEs with a located fix in total; 2 of them changed StandardContext.
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/tomcat 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