Some HTTP/2 implementations are vulnerable to a settings flood, potentially leading to a denial of service. The attacker sends a stream of SETTINGS frames to the peer. Since the RFC requires that the peer reply with one acknowledgement per SETTINGS frame, an empty SETTINGS frame is almost equivalent in behavior to a ping. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both.
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)
|
Information
Published : 2019-08-13 14:15
Updated : 2022-08-12 11:40
NVD link : CVE-2019-9515
Mitre link : CVE-2019-9515
JSON object : View
CWE
CWE-770
Allocation of Resources Without Limits or Throttling
Products Affected
oracle
- graalvm
redhat
- jboss_enterprise_application_platform
- quay
- enterprise_linux
- jboss_core_services
- single_sign-on
- openstack
- openshift_service_mesh
- openshift_container_platform
- software_collections
canonical
- ubuntu_linux
opensuse
- leap
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
f5
- big-ip_local_traffic_manager