Skip to content

Apache Tomcat may reject request containing invalid Content-Length header

High severity GitHub Reviewed Published Nov 1, 2022 to the GitHub Advisory Database • Updated Apr 23, 2024

Package

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

Affected versions

>= 8.5.0, < 8.5.83
>= 9.0.0-M1, < 9.0.68
>= 10.0.0-M1, < 10.0.27
>= 10.1.0-M1, < 10.1.1

Patched versions

8.5.83
9.0.68
10.0.27
10.1.1
maven org.apache.tomcat:tomcat-coyote (Maven)
>= 9.0.0-M1, < 9.0.68
>= 10.0.0-M1, < 10.0.27
>= 10.1.0-M1, < 10.1.1
9.0.68
10.0.27
10.1.1

Description

If Apache Tomcat 8.5.0 to 8.5.82, 9.0.0-M1 to 9.0.67, 10.0.0-M1 to 10.0.26 or 10.1.0-M1 to 10.1.0 was configured to ignore invalid HTTP headers via setting rejectIllegalHeader to false (the default for 8.5.x only), Tomcat did not reject a request containing an invalid Content-Length header making a request smuggling attack possible if Tomcat was located behind a reverse proxy that also failed to reject the request with the invalid header.

References

Published by the National Vulnerability Database Nov 1, 2022
Published to the GitHub Advisory Database Nov 1, 2022
Reviewed Nov 1, 2022
Last updated Apr 23, 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
None
Scope
Unchanged
Confidentiality
None
Integrity
High
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:H/A:N

EPSS score

0.240%
(62nd percentile)

Weaknesses

CVE ID

CVE-2022-42252

GHSA ID

GHSA-p22x-g9px-3945

Source code

Credits

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