In Apache HTTP Server 2.4.17 to 2.4.34, by sending continuous, large SETTINGS frames a client can occupy a connection, server thread and CPU time without any connection timeout coming to effect. This affects only HTTP/2 connections. A possible mitigation is to not enable the h2 protocol.
https://www.tenable.com/security/tns-2019-09
https://www.oracle.com/technetwork/security-advisory/cpujan2019-5072801.html
https://www.oracle.com/technetwork/security-advisory/cpuapr2019-5072813.html
https://usn.ubuntu.com/3783-1/
https://support.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-hpesbux03909en_us
https://security.netapp.com/advisory/ntap-20190204-0004/
https://httpd.apache.org/security/vulnerabilities_24.html
https://access.redhat.com/errata/RHSA-2019:0367
https://access.redhat.com/errata/RHSA-2019:0366
https://access.redhat.com/errata/RHSA-2018:3558
http://www.securitytracker.com/id/1041713
http://www.securityfocus.com/bid/105414
http://lists.opensuse.org/opensuse-security-announce/2019-07/msg00056.html
http://lists.opensuse.org/opensuse-security-announce/2019-06/msg00030.html