Apache Tomcat request smuggling via malformed content-length
Apache Software Foundation Apache Tomcat
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.tomcat.embed:tomcat-embed-core Maven |
|
|
Apache Software Foundation Apache Tomcat
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.tomcat.embed:tomcat-embed-core Maven |
|
|
| org.apache.tomcat:tomcat-coyote Maven |
|
|
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.
From the CVE record · apache
Affected Apache Tomcat versions did not reject requests with an invalid Content-Length header when rejectIllegalHeader was set to false, which was the default for 8.5.x. An attacker could use such a request for request smuggling if Tomcat was behind a reverse proxy that also failed to reject the invalid header.
Check deployments of Apache Tomcat 8.5.0–8.5.82, 9.0.0-M1–9.0.67, 10.0.0-M1–10.0.26, or 10.1.0-M1–10.1.0, including the affected tomcat-embed-core and tomcat-coyote Maven packages.