First published: Thu Aug 10 2017(Updated: )
The HTTP/2 header parser in Apache Tomcat 9.0.0.M1 to 9.0.0.M11 and 8.5.0 to 8.5.6 entered an infinite loop if a header was received that was larger than the available buffer. This made a denial of service attack possible.
Credit: security@apache.org security@apache.org security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
Apache Tomcat | =8.5.0 | |
Apache Tomcat | =8.5.1 | |
Apache Tomcat | =8.5.2 | |
Apache Tomcat | =8.5.3 | |
Apache Tomcat | =8.5.4 | |
Apache Tomcat | =8.5.5 | |
Apache Tomcat | =8.5.6 | |
Apache Tomcat | =9.0.0-m1 | |
Apache Tomcat | =9.0.0-m10 | |
Apache Tomcat | =9.0.0-m11 | |
Apache Tomcat | =9.0.0-m2 | |
Apache Tomcat | =9.0.0-m3 | |
Apache Tomcat | =9.0.0-m4 | |
Apache Tomcat | =9.0.0-m5 | |
Apache Tomcat | =9.0.0-m6 | |
Apache Tomcat | =9.0.0-m7 | |
Apache Tomcat | =9.0.0-m8 | |
Apache Tomcat | =9.0.0-m9 | |
maven/org.apache.tomcat:tomcat | >=8.5.0<8.5.8 | 8.5.8 |
maven/org.apache.tomcat:tomcat | >=9.0.0.M1<=9.0.0.M11 | 9.0.0.M12 |
Apache Tomcat | =9.0.0-milestone1 | |
Apache Tomcat | =9.0.0-milestone10 | |
Apache Tomcat | =9.0.0-milestone11 | |
Apache Tomcat | =9.0.0-milestone2 | |
Apache Tomcat | =9.0.0-milestone3 | |
Apache Tomcat | =9.0.0-milestone4 | |
Apache Tomcat | =9.0.0-milestone5 | |
Apache Tomcat | =9.0.0-milestone6 | |
Apache Tomcat | =9.0.0-milestone7 | |
Apache Tomcat | =9.0.0-milestone8 | |
Apache Tomcat | =9.0.0-milestone9 | |
=8.5.0 | ||
=8.5.1 | ||
=8.5.2 | ||
=8.5.3 | ||
=8.5.4 | ||
=8.5.5 | ||
=8.5.6 | ||
=9.0.0-milestone1 | ||
=9.0.0-milestone10 | ||
=9.0.0-milestone11 | ||
=9.0.0-milestone2 | ||
=9.0.0-milestone3 | ||
=9.0.0-milestone4 | ||
=9.0.0-milestone5 | ||
=9.0.0-milestone6 | ||
=9.0.0-milestone7 | ||
=9.0.0-milestone8 | ||
=9.0.0-milestone9 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.