Security readout for executives and security teams
CVE-2020-11080 is a denial-of-service issue in nghttp2, a common HTTP/2 library. An unauthenticated remote client can trigger high CPU use by repeatedly sending oversized HTTP/2 SETTINGS payloads. The documented impact is limited availability degradation, and the vulnerability is fixed in nghttp2 1.41.0. Exposure is most likely where applications, proxies, or platform packages use nghttp2 before 1.41.0 and accept HTTP/2 connections from untrusted clients. Downstream Linux and Oracle advisories indicate packaged ecosystem exposure, but the bundle only identifies nghttp2 itself as the affected product. Treat this as routine patching unless a critical public HTTP/2 service depends on an affected nghttp2 version. Business risk is service degradation, not data theft. Patch during the next normal maintenance window, faster for high-traffic exposed services. Mitigation focus: Upgrade nghttp2 to version 1.41.0 or a vendor-patched package.; Prioritize internet-facing HTTP/2 services using affected nghttp2 builds.; If upgrading is delayed, implement the documented frame receive callback workaround..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-707: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2020-11080 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Low
- CVSS
- 3.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L2.21.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
3.7LowVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
Source materials
- CVE List V5 sourceCVE List V5
- DSA-4696CVE reference · vendor-advisory
- FEDORA-2020-f7d15c8b77CVE reference · vendor-advisory
- https://www.oracle.com/security-alerts/cpujul2020.htmlCVE reference
- https://github.com/nghttp2/nghttp2/security/advisories/GHSA-q5wr-xfw9-q7xrCVE reference
- https://github.com/nghttp2/nghttp2/commit/336a98feb0d56b9ac54e12736b18785c27f75090CVE reference
- https://github.com/nghttp2/nghttp2/commit/f8da73bd042f810f34d19f9eae02b46d870af394CVE reference
- https://www.oracle.com/security-alerts/cpuoct2020.htmlCVE reference
- FEDORA-2020-43d5a372fcCVE reference · vendor-advisory
- https://www.oracle.com/security-alerts/cpujan2021.htmlCVE reference
- https://www.oracle.com//security-alerts/cpujul2021.htmlCVE reference
- [debian-lts-announce] 20211017 [SECURITY] [DLA 2786-1] nghttp2 security updateCVE reference · mailing-list
- https://www.oracle.com/security-alerts/cpuapr2022.htmlCVE reference
- [debian-lts-announce] 20231016 [SECURITY] [DLA 3621-1] nghttp2 security updateCVE reference · mailing-list
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization
Improper Neutralization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.