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)
|
History
07 Nov 2023, 03:13
Type | Values Removed | Values Added |
---|---|---|
References |
|
|
Information
Published : 2019-08-13 21:15
Updated : 2024-02-28 17:08
NVD link : CVE-2019-9515
Mitre link : CVE-2019-9515
CVE.ORG link : CVE-2019-9515
JSON object : View
Products Affected
redhat
- enterprise_linux
- openshift_container_platform
- jboss_enterprise_application_platform
- openshift_service_mesh
- quay
- openstack
- software_collections
- single_sign-on
- jboss_core_services
apple
- swiftnio
- mac_os_x
apache
- traffic_server
nodejs
- node.js
synology
- vs960hd
- diskstation_manager
- skynas
- vs960hd_firmware
oracle
- graalvm
fedoraproject
- fedora
opensuse
- leap
f5
- big-ip_local_traffic_manager
canonical
- ubuntu_linux
mcafee
- web_gateway
debian
- debian_linux