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

• https://nvd.nist.gov/vuln/detail/CVE-2022-42252
• https://lists.apache.org/thread/zzcxzvqfdqn515zfs3dxb7n8gty589sq
• https://security.gentoo.org/glsa/202305-37
• apache/tomcat@0d089a1
• apache/tomcat@4c7f4fd
• apache/tomcat@a1c0790
• apache/tomcat@c9fe754
• https://tomcat.apache.org/security-10.html
• https://tomcat.apache.org/security-8.html
• https://tomcat.apache.org/security-9.html