7.8
CWE
400
Advisory Published
CVE Published
CVE Published
Updated

CVE-2019-9513: Some HTTP/2 implementations are vulnerable to resource loops, potentially leading to a denial of service

First published: Thu Aug 01 2019(Updated: )

A flaw was found in HTTP/2. An attacker, using PRIORITY frames to flood the system, could cause excessive CPU usage and starvation of other clients. The largest threat from this vulnerability is to system availability.

Credit: cret@cert.org cret@cert.org cret@cert.org

Affected SoftwareAffected VersionHow to fix
redhat/jbcs-httpd24-httpd<0:2.4.29-41.jbcs.el6
0:2.4.29-41.jbcs.el6
redhat/jbcs-httpd24-nghttp2<0:1.39.2-1.jbcs.el6
0:1.39.2-1.jbcs.el6
redhat/jbcs-httpd24-apr<0:1.6.3-63.jbcs.el6
0:1.6.3-63.jbcs.el6
redhat/jbcs-httpd24-apr-util<0:1.6.1-48.jbcs.el6
0:1.6.1-48.jbcs.el6
redhat/jbcs-httpd24-brotli<0:1.0.6-7.jbcs.el6
0:1.0.6-7.jbcs.el6
redhat/jbcs-httpd24-curl<0:7.64.1-14.jbcs.el6
0:7.64.1-14.jbcs.el6
redhat/jbcs-httpd24-httpd<0:2.4.37-33.jbcs.el6
0:2.4.37-33.jbcs.el6
redhat/jbcs-httpd24-jansson<0:2.11-20.jbcs.el6
0:2.11-20.jbcs.el6
redhat/jbcs-httpd24-nghttp2<0:1.39.2-4.jbcs.el6
0:1.39.2-4.jbcs.el6
redhat/jbcs-httpd24-openssl<1:1.1.1-25.jbcs.el6
1:1.1.1-25.jbcs.el6
redhat/jbcs-httpd24-httpd<0:2.4.29-41.jbcs.el7
0:2.4.29-41.jbcs.el7
redhat/jbcs-httpd24-nghttp2<0:1.39.2-1.jbcs.el7
0:1.39.2-1.jbcs.el7
redhat/jbcs-httpd24-apr<0:1.6.3-63.jbcs.el7
0:1.6.3-63.jbcs.el7
redhat/jbcs-httpd24-apr-util<0:1.6.1-48.jbcs.el7
0:1.6.1-48.jbcs.el7
redhat/jbcs-httpd24-brotli<0:1.0.6-7.jbcs.el7
0:1.0.6-7.jbcs.el7
redhat/jbcs-httpd24-curl<0:7.64.1-14.jbcs.el7
0:7.64.1-14.jbcs.el7
redhat/jbcs-httpd24-httpd<0:2.4.37-33.jbcs.el7
0:2.4.37-33.jbcs.el7
redhat/jbcs-httpd24-jansson<0:2.11-20.jbcs.el7
0:2.11-20.jbcs.el7
redhat/jbcs-httpd24-nghttp2<0:1.39.2-4.jbcs.el7
0:1.39.2-4.jbcs.el7
redhat/jbcs-httpd24-openssl<1:1.1.1-25.jbcs.el7
1:1.1.1-25.jbcs.el7
redhat/kiali<0:v1.0.6.redhat1-1.el7
0:v1.0.6.redhat1-1.el7
redhat/servicemesh<0:1.0.1-8.el8
0:1.0.1-8.el8
redhat/servicemesh-cni<0:1.0.1-8.el8
0:1.0.1-8.el8
redhat/servicemesh-grafana<0:6.2.2-21.el8
0:6.2.2-21.el8
redhat/servicemesh-operator<0:1.0.1-8.el8
0:1.0.1-8.el8
redhat/servicemesh-prometheus<0:2.7.2-22.el8
0:2.7.2-22.el8
redhat/servicemesh-proxy<0:1.0.1-7.el8
0:1.0.1-7.el8
redhat/nghttp2<0:1.33.0-1.el8_0.1
0:1.33.0-1.el8_0.1
redhat/rh-nginx110-nginx<1:1.10.2-9.el6.1
1:1.10.2-9.el6.1
redhat/httpd24-httpd<0:2.4.34-8.el6.1
0:2.4.34-8.el6.1
redhat/httpd24-nghttp2<0:1.7.1-7.el6.1
0:1.7.1-7.el6.1
redhat/rh-nginx110-nginx<1:1.10.2-9.el7.1
1:1.10.2-9.el7.1
redhat/rh-nginx112-nginx<1:1.12.1-3.el7.1
1:1.12.1-3.el7.1
redhat/rh-nginx114-nginx<1:1.14.1-1.el7.1
1:1.14.1-1.el7.1
redhat/rh-nodejs10<0:3.2-3.el7
0:3.2-3.el7
redhat/rh-nodejs10-nodejs<0:10.16.3-3.el7
0:10.16.3-3.el7
redhat/httpd24-httpd<0:2.4.34-8.el7.1
0:2.4.34-8.el7.1
redhat/httpd24-nghttp2<0:1.7.1-7.el7.1
0:1.7.1-7.el7.1
redhat/rh-nodejs8<0:3.0-5.el7
0:3.0-5.el7
redhat/rh-nodejs8-nodejs<0:8.16.1-2.el7
0:8.16.1-2.el7
redhat/envoy<1.11.1
1.11.1
redhat/Nodejs<8.16.1
8.16.1
redhat/Nodejs<10.16.3
10.16.3
redhat/Nodejs<12.8.1
12.8.1
redhat/nginx<1.16.1
1.16.1
redhat/nginx<1.17.3
1.17.3
redhat/nghttp2<1.39.2
1.39.2
debian/nghttp2
1.43.0-1+deb11u1
1.43.0-1+deb11u2
1.52.0-1+deb12u2
1.52.0-1+deb12u1
1.64.0-1
debian/nginx
1.18.0-6.1+deb11u3
1.22.1-9
1.26.3-2
debian/nodejs
12.22.12~dfsg-1~deb11u4
12.22.12~dfsg-1~deb11u5
18.19.0+dfsg-6~deb12u2
18.19.0+dfsg-6~deb12u1
20.18.2+dfsg-4
20.18.3+dfsg-1
All of
SwiftNIO>=1.0.0<=1.4.0
Any of
Apple iOS and macOS>=10.12
Ubuntu>=14.04
Apache Traffic Server>=6.0.0<=6.2.3
Apache Traffic Server>=7.0.0<=7.1.6
Apache Traffic Server>=8.0.0<=8.0.3
Ubuntu=16.04
Ubuntu=18.04
Ubuntu=19.04
Debian=9.0
Debian=10.0
Fedora=30
synology skynas
Synology DiskStation Manager=6.2
All of
synology vs960hd firmware
synology vs960hd
Fedora=29
openSUSE=15.0
openSUSE=15.1
redhat jboss core services=1.0
redhat jboss enterprise application platform=7.2.0
redhat jboss enterprise application platform=7.3.0
redhat openshift service mesh=1.0
redhat quay=3.0.0
redhat software collections=1.0
Red Hat Enterprise Linux=8.0
Oracle GraalVM Enterprise Edition=19.2.0
McAfee Web Gateway>=7.7.2.0<7.7.2.24
McAfee Web Gateway>=7.8.2.0<7.8.2.13
McAfee Web Gateway>=8.1.0<8.2.0
F5 NGINX App Protect>=1.9.5<1.16.1
F5 NGINX App Protect>=1.17.0<=1.17.2
Oracle Enterprise Communications Broker=3.1.0
Oracle Enterprise Communications Broker=3.2.0
Node.js>=8.0.0<=8.8.1
Node.js>=8.9.0<8.16.1
Node.js>=10.0.0<=10.12.0
Node.js>=10.13.0<10.16.3
Node.js>=12.0.0<12.8.1
SwiftNIO>=1.0.0<=1.4.0
Apple iOS and macOS>=10.12
Ubuntu>=14.04
Synology DiskStation Manager=6.2
synology vs960hd firmware
synology vs960hd

Remedy

Red Hat Quay 3.0 uses Nginx 1.12 from Red Hat Software Collections. It will be updated once a fixed is released for Software Collections. In the meantime users of Quay can disable http/2 support in Nginx by following these instructions: 1. Copy the Nginx configuration from the quay container to the host $ docker cp 3aadf1421ba3:/quay-registry/conf/nginx/ /mnt/quay/nginx 2. Edit the Nginx configuration, removing http/2 support $ sed -i 's/http2 //g' /mnt/quay/nginx/nginx.conf 3. Restart Nginx with the new configuration mounted into the container, eg: $ docker run --restart=always -p 443:8443 -p 80:8080 --sysctl net.core.somaxconn=4096 -v /mnt/quay/config:/conf/stack:Z -v /mnt/quay/storage:/datastorage -v /mnt/quay/nginx:/quay-registry/config/nginx:Z -d quay.io/redhat/quay:v3.0.3

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2019-9513?

    The severity of CVE-2019-9513 is critical due to its potential impact on system availability and resource exhaustion.

  • How do I fix CVE-2019-9513?

    To fix CVE-2019-9513, you should upgrade to the latest versions of the affected software packages as specified in the security advisories.

  • What are the impacted products associated with CVE-2019-9513?

    Products affected by CVE-2019-9513 include various versions of Apache HTTP Server, nghttp2, and several other software packages related to HTTP/2 implementation.

  • Who is affected by CVE-2019-9513?

    Any systems utilizing affected versions of HTTP/2 implementations, especially in web server environments, are vulnerable to CVE-2019-9513.

  • Is there a workaround for CVE-2019-9513?

    Currently, the recommended action is to apply the relevant patches, as there are no known effective workarounds for CVE-2019-9513.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203