The HTTP/2 implementation in Apache Tomcat 9.0.0.M1 to 9.0.14 and 8.5.0 to 8.5.37 accepted streams with excessive numbers of SETTINGS frames and also permitted clients to keep streams open without reading/writing request/response data. By keeping streams open for requests that utilised the Servlet API's blocking I/O, clients were able to cause server-side threads to block eventually leading to thread exhaustion and a DoS.
https://www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html
https://www.oracle.com/security-alerts/cpujan2020.html
https://www.oracle.com/security-alerts/cpuapr2020.html
https://www.debian.org/security/2019/dsa-4596
https://support.f5.com/csp/article/K17321505
https://security.netapp.com/advisory/ntap-20190419-0001/
https://seclists.org/bugtraq/2019/Dec/43
https://access.redhat.com/errata/RHSA-2019:3931
https://access.redhat.com/errata/RHSA-2019:3929
http://www.securityfocus.com/bid/107674
http://lists.opensuse.org/opensuse-security-announce/2019-07/msg00054.html
http://lists.opensuse.org/opensuse-security-announce/2019-07/msg00013.html
http://lists.opensuse.org/opensuse-security-announce/2019-06/msg00090.html