In nghttp2 before version 1.41.0, the overly large HTTP/2 SETTINGS frame payload causes denial of service. The proof of concept attack involves a malicious client constructing a SETTINGS frame with a length of 14,400 bytes (2400 individual settings entries) over and over again. The attack causes the CPU to spike at 100%. nghttp2 v1.41.0 fixes this vulnerability. There is a workaround to this vulnerability. Implement nghttp2_on_frame_recv_callback callback, and if received frame is SETTINGS frame and the number of settings entries are large (e.g., > 32), then drop the connection.
References
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Configuration 3 (hide)
|
Configuration 4 (hide)
|
Configuration 5 (hide)
|
Configuration 6 (hide)
|
History
07 Nov 2023, 03:14
Type | Values Removed | Values Added |
---|---|---|
References |
|
|
16 Oct 2023, 18:15
Type | Values Removed | Values Added |
---|---|---|
References |
|
Information
Published : 2020-06-03 23:15
Updated : 2024-02-28 17:47
NVD link : CVE-2020-11080
Mitre link : CVE-2020-11080
CVE.ORG link : CVE-2020-11080
JSON object : View
Products Affected
oracle
- graalvm
- banking_extensibility_workbench
- blockchain_platform
- mysql
- enterprise_communications_broker
opensuse
- leap
nghttp2
- nghttp2
debian
- debian_linux
nodejs
- node.js
fedoraproject
- fedora