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 as

Summary

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.

Timeline

1. Apr 17, 2017, 4:00 PM UTCCVE published
2. Aug 5, 2024, 3:11 PM UTCRecord last updated

Affected versions

• Apache Software Foundation Apache Tomcat

  9.0.0.M1 to 9.0.0.M18, 8.5.0 to 8.5.12

• org.apache.tomcat:tomcatMaven

  From 9.0.0.M1 · fixed in 9.0.0.M19

• org.apache.tomcat:tomcatMaven

  From 8.5.0 · fixed in 8.5.13

References 13