Incorrect Transfer-Encoding handling with HTTP/1.0
Apache Software Foundation Apache Tomcat
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.tomcat:tomcat Maven |
|
|
Apache Software Foundation Apache Tomcat
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.tomcat:tomcat Maven |
|
|
Apache Tomcat 10.0.0-M1 to 10.0.6, 9.0.0.M1 to 9.0.46 and 8.5.0 to 8.5.66 did not correctly parse the HTTP transfer-encoding request header in some circumstances leading to the possibility to request smuggling when used with a reverse proxy. Specifically: - Tomcat incorrectly ignored the transfer encoding header if the client declared it would only accept an HTTP/1.0 response; - Tomcat honoured the identify encoding; and - Tomcat did not ensure that, if present, the chunked encoding was the final encoding.
From the CVE record · apache
Apache Tomcat can incorrectly parse the HTTP Transfer-Encoding request header. When Tomcat is used with a reverse proxy, an attacker can send crafted HTTP requests that may enable request smuggling. The input does not specify an authentication or user-interaction requirement.
Check Maven deployments of org.apache.tomcat:tomcat versions >=10.0.0-M1 and <10.0.7, >=9.0.0-M1 and <9.0.48, or >=8.5.0 and <8.5.68.