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.
The product does not release or incorrectly releases a resource before it is made available for re-use.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Tomcat | Apache | 8.5.0 (including) | 8.5.0 (including) |
| Tomcat | Apache | 8.5.1 (including) | 8.5.1 (including) |
| Tomcat | Apache | 8.5.2 (including) | 8.5.2 (including) |
| Tomcat | Apache | 8.5.3 (including) | 8.5.3 (including) |
| Tomcat | Apache | 8.5.4 (including) | 8.5.4 (including) |
| Tomcat | Apache | 8.5.5 (including) | 8.5.5 (including) |
| Tomcat | Apache | 8.5.6 (including) | 8.5.6 (including) |
| Tomcat | Apache | 8.5.7 (including) | 8.5.7 (including) |
| Tomcat | Apache | 8.5.8 (including) | 8.5.8 (including) |
| Tomcat | Apache | 8.5.9 (including) | 8.5.9 (including) |
| Tomcat | Apache | 8.5.10 (including) | 8.5.10 (including) |
| Tomcat | Apache | 8.5.11 (including) | 8.5.11 (including) |
| Tomcat | Apache | 8.5.12 (including) | 8.5.12 (including) |