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.
Metrics
Affected Vendors & Products
Advisories
Source | ID | Title |
---|---|---|
![]() |
DLA-3384-1 | tomcat9 security update |
![]() |
DSA-5381-1 | tomcat9 security update |
![]() |
EUVD-2022-7390 | 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. |
![]() |
GHSA-p22x-g9px-3945 | Apache Tomcat may reject request containing invalid Content-Length header |
![]() |
USN-6880-1 | Tomcat vulnerability |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Tue, 06 May 2025 15:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Metrics |
ssvc
|

Status: PUBLISHED
Assigner: apache
Published:
Updated: 2025-05-06T15:09:20.374Z
Reserved: 2022-10-03T00:00:00.000Z
Link: CVE-2022-42252

Updated: 2024-08-03T13:03:45.683Z

Status : Modified
Published: 2022-11-01T09:15:10.817
Modified: 2025-05-06T16:15:26.137
Link: CVE-2022-42252


No data.