CVE-2019-9516: Some HTTP/2 implementations are vulnerable to a header leak, potentially leading to a denial of service

Published Aug 13, 2019
·
Updated

A flaw was found in HTTP/2. An attacker, sending a stream of header with a 0-length header name and a 0-length header value, could cause some implementations to allocate memory for these headers and keep the allocations alive until the session dies. The can consume excess memory, potentially leading to a denial of service. The highest threat from this vulnerability is to system availability.

Other sources

A vulnerability was found in http/2 where an attacker sends a stream of headers with a 0-length header name and 0-length header value, optionally Huffman encoded into 1-byte or greater headers. Some implementations allocate memory for these headers and keep the allocation alive until the session dies. This can consume excess memory, potentially leading to a denial of service.

— Red Hat

Netflix has discovered several resource exhaustion vectors affecting a variety of third-party HTTP/2 implementations. These attack vectors can be used to launch DoS attacks against servers that support HTTP/2 communication. Netflix worked with Google and CERT/CC to coordinate disclosure to the Internet community.

— Node.Js

Some HTTP/2 implementations are vulnerable to a header leak, potentially leading to a denial of service. The attacker sends a stream of headers with a 0-length header name and 0-length header value, optionally Huffman encoded into 1-byte or greater headers. Some implementations allocate memory for these headers and keep the allocation alive until the session dies. This can consume excess memory.

Affected Software

82 affected componentsFixes available
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/rh-nginx110-nginx<1:1.10.2-9.el6.1
1:1.10.2-9.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/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
All of the following
Apple Swiftnio>=1.0.0<=1.4.0
Any of the following
Apple iOS and macOS>=10.12
Canonical Ubuntu Linux>=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
Canonical Ubuntu Linux=16.04
Canonical Ubuntu Linux=18.04
Canonical Ubuntu Linux=19.04
Debian Debian Linux=9.0
Debian Debian Linux=10.0
Fedoraproject Fedora=30
Synology Skynas
Synology DiskStation Manager=6.2
All of the following
Synology Vs960hd Firmware
Synology Vs960hd
Fedoraproject Fedora=29
Fedoraproject Fedora=32
openSUSE Leap=15.0
openSUSE Leap=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
redhat Enterprise Linux=8.0
Oracle GraalVM=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>=1.9.5<1.16.1
F5 Nginx>=1.17.0<=1.17.2
Nodejs Node.js>=8.0.0<8.16.1
Nodejs Node.js>=10.0.0<10.16.3
Nodejs Node.js>=12.0.0<12.8.1
Apple Swiftnio>=1.0.0<=1.4.0
Apple iOS and macOS>=10.12
Canonical Ubuntu Linux>=14.04
Synology DiskStation Manager=6.2
Synology Vs960hd Firmware
Synology Vs960hd
debian/nginx
1.18.0-6.1+deb11u31.18.0-6.1+deb11u51.22.1-9+deb12u31.22.1-9+deb12u41.26.3-3+deb13u11.26.3-3+deb13u21.28.2-2
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
Node.js Node.js>=8.0.0<8.16.1, >=10.0.0<10.16.3, >=12.0.0<12.8.1
8.16.110.16.312.8.1
Node.js Node.js>=10.0.0<10.16.3
10.16.3
Node.js Node.js>=12.0.0<12.8.1
12.8.1
Node.js Node.js>=8.0.0<8.16.1
8.16.1
All of the following
Apple Swiftnio>=1.0.0<=1.4.0
Canonical Ubuntu Linux>=14.04

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/jbcs-httpd24-httpd to a version that resolves this vulnerability.

    Fixed in 0:2.4.29-41.jbcs.el6
  2. Upgrade

    Upgrade redhat/jbcs-httpd24-nghttp2 to a version that resolves this vulnerability.

    Fixed in 0:1.39.2-1.jbcs.el6
  3. Upgrade

    Upgrade redhat/jbcs-httpd24-apr to a version that resolves this vulnerability.

    Fixed in 0:1.6.3-63.jbcs.el6
  4. Upgrade

    Upgrade redhat/jbcs-httpd24-apr-util to a version that resolves this vulnerability.

    Fixed in 0:1.6.1-48.jbcs.el6
  5. Upgrade

    Upgrade redhat/jbcs-httpd24-brotli to a version that resolves this vulnerability.

    Fixed in 0:1.0.6-7.jbcs.el6
  6. Upgrade

    Upgrade redhat/jbcs-httpd24-curl to a version that resolves this vulnerability.

    Fixed in 0:7.64.1-14.jbcs.el6
  7. Upgrade

    Upgrade redhat/jbcs-httpd24-httpd to a version that resolves this vulnerability.

    Fixed in 0:2.4.37-33.jbcs.el6
  8. Upgrade

    Upgrade redhat/jbcs-httpd24-jansson to a version that resolves this vulnerability.

    Fixed in 0:2.11-20.jbcs.el6
  9. Upgrade

    Upgrade redhat/jbcs-httpd24-nghttp2 to a version that resolves this vulnerability.

    Fixed in 0:1.39.2-4.jbcs.el6
  10. Upgrade

    Upgrade redhat/jbcs-httpd24-openssl to a version that resolves this vulnerability.

    Fixed in 1:1.1.1-25.jbcs.el6
  11. Upgrade

    Upgrade redhat/jbcs-httpd24-httpd to a version that resolves this vulnerability.

    Fixed in 0:2.4.29-41.jbcs.el7
  12. Upgrade

    Upgrade redhat/jbcs-httpd24-nghttp2 to a version that resolves this vulnerability.

    Fixed in 0:1.39.2-1.jbcs.el7
  13. Upgrade

    Upgrade redhat/jbcs-httpd24-apr to a version that resolves this vulnerability.

    Fixed in 0:1.6.3-63.jbcs.el7
  14. Upgrade

    Upgrade redhat/jbcs-httpd24-apr-util to a version that resolves this vulnerability.

    Fixed in 0:1.6.1-48.jbcs.el7
  15. Upgrade

    Upgrade redhat/jbcs-httpd24-brotli to a version that resolves this vulnerability.

    Fixed in 0:1.0.6-7.jbcs.el7
  16. Upgrade

    Upgrade redhat/jbcs-httpd24-curl to a version that resolves this vulnerability.

    Fixed in 0:7.64.1-14.jbcs.el7
  17. Upgrade

    Upgrade redhat/jbcs-httpd24-httpd to a version that resolves this vulnerability.

    Fixed in 0:2.4.37-33.jbcs.el7
  18. Upgrade

    Upgrade redhat/jbcs-httpd24-jansson to a version that resolves this vulnerability.

    Fixed in 0:2.11-20.jbcs.el7
  19. Upgrade

    Upgrade redhat/jbcs-httpd24-nghttp2 to a version that resolves this vulnerability.

    Fixed in 0:1.39.2-4.jbcs.el7
  20. Upgrade

    Upgrade redhat/jbcs-httpd24-openssl to a version that resolves this vulnerability.

    Fixed in 1:1.1.1-25.jbcs.el7
  21. Upgrade

    Upgrade redhat/rh-nginx110-nginx to a version that resolves this vulnerability.

    Fixed in 1:1.10.2-9.el6.1
  22. Upgrade

    Upgrade redhat/rh-nginx110-nginx to a version that resolves this vulnerability.

    Fixed in 1:1.10.2-9.el7.1
  23. Upgrade

    Upgrade redhat/rh-nginx112-nginx to a version that resolves this vulnerability.

    Fixed in 1:1.12.1-3.el7.1
  24. Upgrade

    Upgrade redhat/rh-nginx114-nginx to a version that resolves this vulnerability.

    Fixed in 1:1.14.1-1.el7.1
  25. Upgrade

    Upgrade redhat/rh-nodejs10 to a version that resolves this vulnerability.

    Fixed in 0:3.2-3.el7
  26. Upgrade

    Upgrade redhat/rh-nodejs10-nodejs to a version that resolves this vulnerability.

    Fixed in 0:10.16.3-3.el7
  27. Upgrade

    Upgrade redhat/rh-nodejs8 to a version that resolves this vulnerability.

    Fixed in 0:3.0-5.el7
  28. Upgrade

    Upgrade redhat/rh-nodejs8-nodejs to a version that resolves this vulnerability.

    Fixed in 0:8.16.1-2.el7
  29. Upgrade

    Upgrade debian/nginx to a version that resolves this vulnerability.

    Fixed in 1.18.0-6.1+deb11u3Fixed in 1.18.0-6.1+deb11u5Fixed in 1.22.1-9+deb12u3Fixed in 1.22.1-9+deb12u4Fixed in 1.26.3-3+deb13u1Fixed in 1.26.3-3+deb13u2Fixed in 1.28.2-2
  30. Upgrade

    Upgrade redhat/Nodejs to a version that resolves this vulnerability.

    Fixed in 8.16.1
  31. Upgrade

    Upgrade redhat/Nodejs to a version that resolves this vulnerability.

    Fixed in 10.16.3
  32. Upgrade

    Upgrade redhat/Nodejs to a version that resolves this vulnerability.

    Fixed in 12.8.1
  33. Upgrade

    Upgrade redhat/nginx to a version that resolves this vulnerability.

    Fixed in 1.16.1
  34. Upgrade

    Upgrade redhat/nginx to a version that resolves this vulnerability.

    Fixed in 1.17.3
  35. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 8.16.1Fixed in 10.16.3Fixed in 12.8.1
  36. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.16.3
  37. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 12.8.1
  38. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 8.16.1
  39. Configuration

    Edit /mnt/quay/nginx/nginx.conf and remove the 'http2 ' directive, for example with: sed -i 's/http2 //g' /mnt/quay/nginx/nginx.conf

    Nginx in Red Hat Quay 3.0 HTTP/2 support = disabled
  40. Operational

    Copy the Nginx configuration from container 3aadf1421ba3 to the host with: docker cp 3aadf1421ba3:/quay-registry/conf/nginx/ /mnt/quay/nginx

  41. Operational

    Restart Quay/Nginx with the updated configuration mounted into the container, including -v /mnt/quay/nginx:/quay-registry/config/nginx:Z.

Event History

Aug 13, 2019
CVE Published
12:00 AM
CVE Published
via MITRE·08:50 PM
Data Sourced
via MITRE·08:50 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:15 PM
DescriptionSeverityWeaknessAffected Software
Aug 15, 2019
Data Sourced
via Node.js·12:00 AM
DescriptionSeverityWeaknessAffected Software
Aug 16, 2019
Data Sourced
via Red Hat·09:48 AM
DescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is CVE-2019-9516?

CVE-2019-9516 is a vulnerability in HTTP/2 that allows an attacker to cause a denial of service.

2

How does CVE-2019-9516 work?

CVE-2019-9516 works by sending a stream of headers with 0-length header names and values, potentially causing a header leak and leading to a denial of service.

3

Which software is affected by CVE-2019-9516?

Node.js versions up to 8.16.1, 10.16.3, and 12.8.1, as well as Nginx versions 1.16.1 and 1.17.3 are affected by CVE-2019-9516.

4

How severe is CVE-2019-9516?

CVE-2019-9516 has a severity rating of high, with a CVSS score of 6.5.

5

Are there any references for CVE-2019-9516?

Yes, you can find references for CVE-2019-9516 in the following links: [link1], [link2], [link3].

Company

Resources

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203