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.
References
Configurations
Configuration 1 (hide)
AND |
|
Configuration 2 (hide)
|
Configuration 3 (hide)
|
Configuration 4 (hide)
|
Configuration 5 (hide)
|
Configuration 6 (hide)
AND |
|
Configuration 7 (hide)
|
Configuration 8 (hide)
|
Configuration 9 (hide)
|
Configuration 10 (hide)
|
Configuration 11 (hide)
|
Configuration 12 (hide)
|
Configuration 13 (hide)
|
Configuration 14 (hide)
|
Information
Published : 2019-08-13 14:15
Updated : 2022-08-05 07:52
NVD link : CVE-2019-9516
Mitre link : CVE-2019-9516
JSON object : View
CWE
CWE-770
Allocation of Resources Without Limits or Throttling
Products Affected
oracle
- graalvm
f5
- nginx
redhat
- jboss_enterprise_application_platform
- quay
- enterprise_linux
- jboss_core_services
- openshift_service_mesh
- software_collections
canonical
- ubuntu_linux
mcafee
- web_gateway
synology
- vs960hd
- vs960hd_firmware
- skynas
- diskstation_manager
fedoraproject
- fedora
apple
- swiftnio
- mac_os_x
debian
- debian_linux
nodejs
- node.js
apache
- traffic_server
opensuse
- leap