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. Affected versions: 8.5.0 to 8.5.12 Upstream fix: https://svn.apache.org/viewvc?view=revision&revision=1788480 Reference: https://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.5.13
Created tomcat tracking bugs for this issue: Affects: fedora-all [bug 1441242]