How many CVEs have patched parseRequestLine?

2 published CVEs changed parseRequestLine in apache/tomcat, in 6 distinct patches totalling 94 changed lines, between 2011 and 2017.

What is the latest CVE that changed parseRequestLine?

CVE-2016-6816 (Improper Input Validation in Apache Tomcat), published 2017-03-20, changed lines 415 to 524 of java/org/apache/coyote/http11/Http11InputBuffer.java.

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

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

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

4 files

parseRequestLine

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

Defined in 4 files

Last patched March 20, 2017

2

CVEs

That changed this function

6

Distinct patches

Backports counted once

94

Lines changed

Added plus removed

2011–2017

Years

By CVE publication date

Overview

parseRequestLine in apache/tomcat was changed by 2 published CVE fixes between 2011 and 2017, in 6 distinct patches that added or removed 94 lines in total.

The name occurs in 4 files: java/org/apache/coyote/http11/InternalNioInputBuffer.java, java/org/apache/coyote/http11/InternalInputBuffer.java, java/org/apache/coyote/http11/InternalAprInputBuffer.java, java/org/apache/coyote/http11/Http11InputBuffer.java.

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 parseRequestLine, newest first, with the lines each fix touched.

Improper Input Validation in Apache Tomcat
CVE-2016-6816 · java/org/apache/coyote/http11/Http11InputBuffer.java · lines 415–524 · +6 −2 in 4 hunks
High · CVSS 7.1
EPSS 39.6%2017-03-20
Improper Input Validation in Apache Tomcat
CVE-2016-6816 · java/org/apache/coyote/http11/InternalAprInputBuffer.java · lines 181–302 · +10 −7 in 6 hunks
High · CVSS 7.1
EPSS 39.6%2017-03-20
Improper Input Validation in Apache Tomcat
CVE-2016-6816 · java/org/apache/coyote/http11/InternalInputBuffer.java · lines 85–254 · +11 −9 in 7 hunks
High · CVSS 7.1
EPSS 39.6%2017-03-20
Improper Input Validation in Apache Tomcat
CVE-2016-6816 · java/org/apache/coyote/http11/InternalNioInputBuffer.java · lines 221–389 · +15 −12 in 7 hunks
High · CVSS 7.1
EPSS 39.6%2017-03-20
Apache Tomcat does not enforce the maxHttpHeaderSize limit
CVE-2011-0534 · java/org/apache/coyote/http11/InternalNioInputBuffer.java · lines 239–255 · +10 −12
High · CVSS 7.5
EPSS 7.9%2011-02-10

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 files 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 parseRequestLine.

How many CVEs have patched parseRequestLine?: 2 published CVEs changed parseRequestLine in apache/tomcat, in 6 distinct patches totalling 94 changed lines, between 2011 and 2017.
What is the latest CVE that changed parseRequestLine?: CVE-2016-6816 (Improper Input Validation in Apache Tomcat), published 2017-03-20, changed lines 415 to 524 of java/org/apache/coyote/http11/Http11InputBuffer.java.
How does parseRequestLine compare to the rest of apache/tomcat?: apache/tomcat has 135 CVEs with a located fix in total; 2 of them changed parseRequestLine.
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