Potential HTTP request smuggling in Apache Tomcat
Apache Tomcat
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.tomcat.embed:tomcat-embed-core Maven |
|
|
| org.apache.tomcat:tomcat Maven |
Apache Tomcat
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.tomcat.embed:tomcat-embed-core Maven |
|
|
| org.apache.tomcat:tomcat Maven |
< 7.0.100≥ 8.0.0 · < 8.5.51≥ 9.0.0 · < 9.0.31
|
In Apache Tomcat 9.0.0.M1 to 9.0.30, 8.5.0 to 8.5.50 and 7.0.0 to 7.0.99 the HTTP header parsing code used an approach to end-of-line parsing that allowed some invalid HTTP headers to be parsed as valid. This led to a possibility of HTTP Request Smuggling if Tomcat was located behind a reverse proxy that incorrectly handled the invalid Transfer-Encoding header in a particular manner. Such a reverse proxy is considered unlikely.
From the CVE record · apache
Apache Tomcat can accept certain invalid HTTP headers as valid. This may allow HTTP request smuggling if Tomcat is behind a reverse proxy that handles an invalid Transfer-Encoding header in a particular way; such a proxy is considered unlikely. The input does not specify authentication or user-interaction requirements.
Check deployments of Apache Tomcat and Maven packages org.apache.tomcat.embed:tomcat-embed-core or org.apache.tomcat:tomcat in the affected 7.0, 8.0–8.5, or 9.0 version ranges.