In Apache Tomcat 9.0.0.M1 to 9.0.0.M18 and 8.5.0 to 8.5.12, the handling of an HTTP/2 GOAWAY frame for a connection did not close streams associated with that connection that were currently waiting for a WINDOW_UPDATE before allowing the application to write more data. These waiting streams each consumed a thread. A malicious client could therefore construct a series of HTTP/2 requests that would consume all available processing threads.
| Vulnerable Product | Search on Vulmon | Subscribe to Product |
|---|---|---|
apache tomcat 8.5.2 |
||
apache tomcat 8.5.9 |
||
apache tomcat 8.5.4 |
||
apache tomcat 8.5.0 |
||
apache tomcat 8.5.10 |
||
apache tomcat 8.5.5 |
||
apache tomcat 8.5.3 |
||
apache tomcat 8.5.6 |
||
apache tomcat 8.5.7 |
||
apache tomcat 8.5.8 |
||
apache tomcat 8.5.12 |
||
apache tomcat 8.5.11 |
||
apache tomcat 8.5.1 |
||
apache tomcat 9.0.0 |
Vulmon