Skip to content

Potential HTTP request smuggling in Apache Tomcat

Moderate severity GitHub Reviewed Published Feb 28, 2020 to the GitHub Advisory Database • Updated Feb 1, 2023

Package

maven org.apache.tomcat.embed:tomcat-embed-core (Maven)

Affected versions

< 7.0.100
>= 8.0.0, < 8.5.51
>= 9.0.0, < 9.0.31

Patched versions

7.0.100
8.5.51
9.0.31
maven org.apache.tomcat:tomcat (Maven)
< 7.0.100
>= 8.0.0, < 8.5.51
>= 9.0.0, < 9.0.31
7.0.100
8.5.51
9.0.31

Description

In Apache Tomcat 9.0.0.M1 to 9.0.30, 8.5.0 to 8.5.50 and 7.0.0 to 7.0.99 the HTTP header parsing code used an approach to end-of-line parsing that allowed some invalid HTTP headers to be parsed as valid. This led to a possibility of HTTP Request Smuggling if Tomcat was located behind a reverse proxy that incorrectly handled the invalid Transfer-Encoding header in a particular manner. Such a reverse proxy is considered unlikely.

References

Published by the National Vulnerability Database Feb 24, 2020
Reviewed Feb 25, 2020
Published to the GitHub Advisory Database Feb 28, 2020
Last updated Feb 1, 2023

Severity

Moderate

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
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

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.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

EPSS score

0.240%
(62nd percentile)

Weaknesses

CVE ID

CVE-2020-1935

GHSA ID

GHSA-qxf4-chvg-4r8r

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.