Skip to content

HTTP Request Smuggling in Apache Tomcat

Moderate severity GitHub Reviewed Published Aug 13, 2021 to the GitHub Advisory Database • Updated Mar 11, 2024

Package

maven org.apache.tomcat:tomcat (Maven)

Affected versions

>= 10.0.0-M1, < 10.0.7
>= 9.0.0-M1, < 9.0.48
>= 8.5.0, < 8.5.68

Patched versions

10.0.7
9.0.48
8.5.68

Description

Apache Tomcat 10.0.0-M1 to 10.0.6, 9.0.0.M1 to 9.0.46 and 8.5.0 to 8.5.66 did not correctly parse the HTTP transfer-encoding request header in some circumstances leading to the possibility to request smuggling when used with a reverse proxy. Specifically: - Tomcat incorrectly ignored the transfer encoding header if the client declared it would only accept an HTTP/1.0 response; - Tomcat honoured the identify encoding; and - Tomcat did not ensure that, if present, the chunked encoding was the final encoding.

References

Published by the National Vulnerability Database Jul 12, 2021
Reviewed Jul 13, 2021
Published to the GitHub Advisory Database Aug 13, 2021
Last updated Mar 11, 2024

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
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
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:L/PR:N/UI:N/S:U/C:N/I:L/A:N

EPSS score

10.885%
(95th percentile)

Weaknesses

CVE ID

CVE-2021-33037

GHSA ID

GHSA-4vww-mc66-62m6

Source code

Credits

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