Improper Input Validation in Apache Tomcat
Apache Software Foundation Apache Tomcat
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.tomcat:tomcat-coyote Maven |
|
|
Apache Software Foundation Apache Tomcat
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.tomcat:tomcat-coyote Maven |
|
|
7.0.736.0.48The code in Apache Tomcat 9.0.0.M1 to 9.0.0.M11, 8.5.0 to 8.5.6, 8.0.0.RC1 to 8.0.38, 7.0.0 to 7.0.72, and 6.0.0 to 6.0.47 that parsed the HTTP request line permitted invalid characters. This could be exploited, in conjunction with a proxy that also permitted the invalid characters but with a different interpretation, to inject data into the HTTP response. By manipulating the HTTP response the attacker could poison a web-cache, perform an XSS attack and/or obtain sensitive information from requests other then their own.
From the CVE record · apache
Apache Tomcat accepts invalid characters in HTTP request lines. A remote attacker can inject data into an HTTP response when a proxy also accepts those characters but interprets them differently, potentially poisoning a web cache, causing XSS, or obtaining sensitive information from other requests. The input does not specify authentication or user-interaction requirements.
Teams running Apache Tomcat or Maven org.apache.tomcat:tomcat-coyote should check versions 9.0.0.M1–9.0.0.M11, 8.5.0–8.5.7, 8.0.0.RC1–8.0.38, 7.0.0–7.0.72, and 6.0.0–6.0.47.