In nghttp2 before version 1.41.0, the overly large HTTP/2 SETTINGS frame payload causes denial of service. The proof of concept attack involves a malicious client constructing a SETTINGS frame with a length of 14,400 bytes (2400 individual settings entries) over and over again. The attack causes the CPU to spike at 100%. nghttp2 v1.41.0 fixes this vulnerability. There is a workaround to this vulnerability. Implement nghttp2_on_frame_recv_callback callback, and if received frame is SETTINGS frame and the number of settings entries are large (e.g., > 32), then drop the connection.
The product does not ensure or incorrectly ensures that structured messages or data are well-formed and that certain security properties are met before being read from an upstream component or sent to a downstream component.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Nghttp2 | Nghttp2 | * | 1.41.0 (excluding) |
| JBoss Core Services on RHEL 6 | RedHat | jbcs-httpd24-curl-0:7.64.1-36.jbcs.el6 | * |
| JBoss Core Services on RHEL 6 | RedHat | jbcs-httpd24-httpd-0:2.4.37-57.jbcs.el6 | * |
| JBoss Core Services on RHEL 6 | RedHat | jbcs-httpd24-mod_cluster-native-0:1.3.14-4.Final_redhat_2.jbcs.el6 | * |
| JBoss Core Services on RHEL 6 | RedHat | jbcs-httpd24-mod_http2-0:1.15.7-3.jbcs.el6 | * |
| JBoss Core Services on RHEL 6 | RedHat | jbcs-httpd24-mod_jk-0:1.2.48-4.redhat_1.jbcs.el6 | * |
| JBoss Core Services on RHEL 6 | RedHat | jbcs-httpd24-mod_md-1:2.0.8-24.jbcs.el6 | * |
| JBoss Core Services on RHEL 6 | RedHat | jbcs-httpd24-mod_security-0:2.9.2-51.GA.jbcs.el6 | * |
| JBoss Core Services on RHEL 6 | RedHat | jbcs-httpd24-nghttp2-0:1.39.2-25.jbcs.el6 | * |
| JBoss Core Services on RHEL 7 | RedHat | jbcs-httpd24-curl-0:7.64.1-36.jbcs.el7 | * |
| JBoss Core Services on RHEL 7 | RedHat | jbcs-httpd24-httpd-0:2.4.37-57.jbcs.el7 | * |
| JBoss Core Services on RHEL 7 | RedHat | jbcs-httpd24-mod_cluster-native-0:1.3.14-4.Final_redhat_2.jbcs.el7 | * |
| JBoss Core Services on RHEL 7 | RedHat | jbcs-httpd24-mod_http2-0:1.15.7-3.jbcs.el7 | * |
| JBoss Core Services on RHEL 7 | RedHat | jbcs-httpd24-mod_jk-0:1.2.48-4.redhat_1.jbcs.el7 | * |
| JBoss Core Services on RHEL 7 | RedHat | jbcs-httpd24-mod_md-1:2.0.8-24.jbcs.el7 | * |
| JBoss Core Services on RHEL 7 | RedHat | jbcs-httpd24-mod_security-0:2.9.2-51.GA.jbcs.el7 | * |
| JBoss Core Services on RHEL 7 | RedHat | jbcs-httpd24-nghttp2-0:1.39.2-25.jbcs.el7 | * |
| JBoss Core Services on RHEL 7 | RedHat | jbcs-httpd24-openssl-pkcs11-0:0.4.10-7.jbcs.el7 | * |
| OpenShift Service Mesh 1.0 | RedHat | servicemesh-proxy-0:1.0.10-3.el8 | * |
| OpenShift Service Mesh 1.1 | RedHat | servicemesh-proxy-0:1.1.2-3.el8 | * |
| Red Hat Enterprise Linux 8 | RedHat | nodejs:10-8020020200617141353.4cda2c84 | * |
| Red Hat Enterprise Linux 8 | RedHat | nodejs:12-8020020200630155331.4cda2c84 | * |
| Red Hat Enterprise Linux 8 | RedHat | nghttp2-0:1.33.0-3.el8_2.1 | * |
| Red Hat Enterprise Linux 8.0 Update Services for SAP Solutions | RedHat | nodejs:10-8000020200617115915.f8e95b4e | * |
| Red Hat Enterprise Linux 8.0 Update Services for SAP Solutions | RedHat | nghttp2-0:1.33.0-1.el8_0.2 | * |
| Red Hat Enterprise Linux 8.1 Extended Update Support | RedHat | nodejs:12-8010020200630154708.c27ad7f8 | * |
| Red Hat Enterprise Linux 8.1 Extended Update Support | RedHat | nodejs:10-8010020200617134056.c27ad7f8 | * |
| Red Hat Enterprise Linux 8.1 Extended Update Support | RedHat | nghttp2-0:1.33.0-3.el8_1.1 | * |
| Red Hat JBoss Core Services 1 | RedHat | nghttp2 | * |
| Red Hat Software Collections for Red Hat Enterprise Linux 6 | RedHat | httpd24-nghttp2-0:1.7.1-8.el6.1 | * |
| Red Hat Software Collections for Red Hat Enterprise Linux 7 | RedHat | httpd24-nghttp2-0:1.7.1-8.el7.1 | * |
| Red Hat Software Collections for Red Hat Enterprise Linux 7 | RedHat | rh-nodejs12-nodejs-0:12.18.2-1.el7 | * |
| Red Hat Software Collections for Red Hat Enterprise Linux 7 | RedHat | rh-nodejs10-nodejs-0:10.21.0-3.el7 | * |
| Red Hat Software Collections for Red Hat Enterprise Linux 7.6 EUS | RedHat | httpd24-nghttp2-0:1.7.1-8.el7.1 | * |
| Red Hat Software Collections for Red Hat Enterprise Linux 7.6 EUS | RedHat | rh-nodejs12-nodejs-0:12.18.2-1.el7 | * |
| Red Hat Software Collections for Red Hat Enterprise Linux 7.6 EUS | RedHat | rh-nodejs10-nodejs-0:10.21.0-3.el7 | * |
| Red Hat Software Collections for Red Hat Enterprise Linux 7.7 EUS | RedHat | httpd24-nghttp2-0:1.7.1-8.el7.1 | * |
| Red Hat Software Collections for Red Hat Enterprise Linux 7.7 EUS | RedHat | rh-nodejs12-nodejs-0:12.18.2-1.el7 | * |
| Red Hat Software Collections for Red Hat Enterprise Linux 7.7 EUS | RedHat | rh-nodejs10-nodejs-0:10.21.0-3.el7 | * |
| Nghttp2 | Ubuntu | bionic | * |
| Nghttp2 | Ubuntu | esm-apps/xenial | * |
| Nghttp2 | Ubuntu | esm-infra/bionic | * |
| Nghttp2 | Ubuntu | focal | * |
| Nghttp2 | Ubuntu | trusty | * |
| Nghttp2 | Ubuntu | xenial | * |
| Nodejs | Ubuntu | bionic | * |
| Nodejs | Ubuntu | eoan | * |
| Nodejs | Ubuntu | groovy | * |
| Nodejs | Ubuntu | hirsute | * |
| Nodejs | Ubuntu | impish | * |
| Nodejs | Ubuntu | mantic | * |
| Nodejs | Ubuntu | trusty | * |
| Nodejs | Ubuntu | xenial | * |
If a message is malformed, it may cause the message to be incorrectly interpreted. Neutralization is an abstract term for any technique that ensures that input (and output) conforms with expectations and is “safe.” This can be done by:
This weakness typically applies in cases where the product prepares a control message that another process must act on, such as a command or query, and malicious input that was intended as data, can enter the control plane instead. However, this weakness also applies to more general cases where there are not always control implications.