Skip to content

Improper Input Validation in Apache Tomcat

High severity GitHub Reviewed Published May 13, 2022 to the GitHub Advisory Database • Updated Feb 22, 2024

Package

maven org.apache.tomcat:tomcat-coyote (Maven)

Affected versions

>= 9.0.0.M1, <= 9.0.0.M11
>= 8.5.0, < 8.5.8
>= 8.0.0RC1, < 8.0.39
>= 7.0.0, < 7.0.73
>= 6.0.0, < 6.0.48

Patched versions

9.0.0.M12
8.5.8
8.0.39
7.0.73
6.0.48

Description

The code in Apache Tomcat 9.0.0.M1 to 9.0.0.M11, 8.5.0 to 8.5.6, 8.0.0.RC1 to 8.0.38, 7.0.0 to 7.0.72, and 6.0.0 to 6.0.47 that parsed the HTTP request line permitted invalid characters. This could be exploited, in conjunction with a proxy that also permitted the invalid characters but with a different interpretation, to inject data into the HTTP response. By manipulating the HTTP response the attacker could poison a web-cache, perform an XSS attack and/or obtain sensitive information from requests other then their own.

References

Published by the National Vulnerability Database Mar 20, 2017
Published to the GitHub Advisory Database May 13, 2022
Reviewed Jul 6, 2022
Last updated Feb 22, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

EPSS score

0.786%
(81st percentile)

Weaknesses

CVE ID

CVE-2016-6816

GHSA ID

GHSA-jc7p-5r39-9477

Source code

No known source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.