GHSA-p22x-g9px-3945 Apache Tomcat may reject request containing invalid Content-Length header

• Maven org.apache.tomcat.embed:tomcat-embed-core: >= 8.5.0, < 8.5.83 → fixed in 8.5.83 • Maven org.apache.tomcat.embed:tomcat-embed-core: >= 9.0.0-M1, < 9.0.68 → fixed in 9.0.68 • Maven org.apache.tomcat.embed:tomcat-embed-core: >= 10.0.0-M1, < 10.0.27 → fixed in 10.0.27 • Maven org.apache.tomcat.embed:tomcat-embed-core: >= 10.1.0-M1, < 10.1.1 → fixed in 10.1.1 • Maven org.apache.tomcat:tomcat-coyote: >= 9.0.0-M1, < 9.0.68 → fixed in 9.0.68 • Maven org.apache.tomcat:tomcat-coyote: >= 10.0.0-M1, < 10.0.27 → fixed in 10.0.27 • Maven org.apache.tomcat:tomcat-coyote: >= 10.1.0-M1, < 10.1.1 → fixed in 10.1.1

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.