Nghttp2 Nghttp2 Nghttp2

stack.watch can notify you when security vulnerabilities are reported in Nghttp2 Nghttp2. You can add multiple products that you use with Nghttp2 to create your own personal software stack watcher.

By the Year

In 2020 there have been 1 vulnerability in Nghttp2 Nghttp2 with an average score of 7.5 out of ten. Last year Nghttp2 had 0 security vulnerabilities published. That is, 1 more vulnerability have already been reported in 2020 as compared to last year.

Year Vulnerabilities Average Score
2020 1 7.50
2019 0 0.00
2018 1 7.50

It may take a day or so for new Nghttp2 vulnerabilities to show up. Additionally vulnerabilities may be tagged under a different product or component name.

Latest Nghttp2 Nghttp2 Security Vulnerabilities

In nghttp2 before version 1.41.0

CVE-2020-11080 7.5 - High - June 03, 2020

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.

Improper Enforcement of Message or Data Structure

nghttp2 version >= 1.10.0 and nghttp2 <= v1.31.0 contains an Improper Input Validation CWE-20 vulnerability in ALTSVC frame handling that can result in segmentation fault leading to denial of service. This attack appears to be exploitable via network client. This vulnerability appears to have been fixed in >= 1.31.1

CVE-2018-1000168 7.5 - High - May 08, 2018

nghttp2 version >= 1.10.0 and nghttp2 <= v1.31.0 contains an Improper Input Validation CWE-20 vulnerability in ALTSVC frame handling that can result in segmentation fault leading to denial of service. This attack appears to be exploitable via network client. This vulnerability appears to have been fixed in >= 1.31.1.

NULL Pointer Dereference