# CVE-2020-11080: Denial of service in nghttp2 > A malicious client can cause a denial of service by sending oversized HTTP/2 SETTINGS frames, leading to high CPU usage. - **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 3 Jun 2020 - **Updated:** 9 Jun 2025 - **Also known as:** ALPINE-CVE-2020-11080, ALSA-2020:2755, BIT-node-2020-11080, BIT-node-min-2020-11080, CLEANSTART-2024-IB47069, CLEANSTART-2026-OX53769, CLEANSTART-2026-QZ70623, DEBIAN-CVE-2020-11080, GHSA-q5wr-xfw9-q7xr, JLSEC-2026-1, MGASA-2020-0256, RHSA-2020:2523, RHSA-2020:2524, RHSA-2020:2755, RHSA-2020:2784, RHSA-2020:2823, RHSA-2020:2850, RLSA-2020:2755, SUSE-SU-2021:0930-1, SUSE-SU-2021:0931-1, UBUNTU-CVE-2020-11080, USN-6142-1, openSUSE-SU-2021:0468-1 ## What is CVE-2020-11080? CVE-2020-11080 is a low-severity denial of service vulnerability in Debian Debian Linux, published on 3 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. Weakness: CWE-400 (Uncontrolled Resource Consumption), CWE-707 (Improper Neutralization) ## Which versions are affected by CVE-2020-11080? 2 open source packages ship an affected version, including node and node-min. It affects 10 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `node` | Bitnami | From 10.13.0 | 10.21.0, 12.18.0, 14.4.1 | | `node-min` | Bitnami | From 10.0.0 | 10.12.1, 10.21.0, 12.12.1, 12.18.0, 14.4.1 | | `libnghttp2` | AlmaLinux:8 | All versions | 1.33.0-3.el8_2.1 | | `libnghttp2-devel` | AlmaLinux:8 | All versions | 1.33.0-3.el8_2.1 | | `nghttp2` | AlmaLinux:8 | All versions | 1.33.0-3.el8_2.1 | | `libnghttp2` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.33.0-3.el8_2.1 | | `libnghttp2-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.33.0-3.el8_2.1 | | `nghttp2` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.33.0-3.el8_2.1 | | `nghttp2-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.33.0-3.el8_2.1 | | `nghttp2-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.33.0-3.el8_2.1 | | `libnghttp2-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:1.33.0-3.el8_2.1 | | `libnghttp2-devel` | Red Hat:enterprise_linux:8::crb | All versions | 0:1.33.0-3.el8_2.1 | | `nghttp2` | Red Hat:enterprise_linux:8::crb | All versions | 0:1.33.0-3.el8_2.1 | | `nghttp2-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:1.33.0-3.el8_2.1 | | `nghttp2-debugsource` | Red Hat:enterprise_linux:8::crb | All versions | 0:1.33.0-3.el8_2.1 | | `libnghttp2` | Red Hat:rhel_e4s:8.0::baseos | All versions | 0:1.33.0-1.el8_0.2 | | `libnghttp2-debuginfo` | Red Hat:rhel_e4s:8.0::baseos | All versions | 0:1.33.0-1.el8_0.2 | | `nghttp2` | Red Hat:rhel_e4s:8.0::baseos | All versions | 0:1.33.0-1.el8_0.2 | | `nghttp2-debuginfo` | Red Hat:rhel_e4s:8.0::baseos | All versions | 0:1.33.0-1.el8_0.2 | | `nghttp2-debugsource` | Red Hat:rhel_e4s:8.0::baseos | All versions | 0:1.33.0-1.el8_0.2 | | `libnghttp2` | Red Hat:rhel_eus:8.1::baseos | All versions | 0:1.33.0-3.el8_1.1 | | `libnghttp2-debuginfo` | Red Hat:rhel_eus:8.1::baseos | All versions | 0:1.33.0-3.el8_1.1 | | `nghttp2` | Red Hat:rhel_eus:8.1::baseos | All versions | 0:1.33.0-3.el8_1.1 | | `nghttp2-debuginfo` | Red Hat:rhel_eus:8.1::baseos | All versions | 0:1.33.0-3.el8_1.1 | | `nghttp2-debugsource` | Red Hat:rhel_eus:8.1::baseos | All versions | 0:1.33.0-3.el8_1.1 | | `libnghttp2-debuginfo` | Red Hat:rhel_eus:8.1::crb | All versions | 0:1.33.0-3.el8_1.1 | | `libnghttp2-devel` | Red Hat:rhel_eus:8.1::crb | All versions | 0:1.33.0-3.el8_1.1 | | `nghttp2` | Red Hat:rhel_eus:8.1::crb | All versions | 0:1.33.0-3.el8_1.1 | | `nghttp2-debuginfo` | Red Hat:rhel_eus:8.1::crb | All versions | 0:1.33.0-3.el8_1.1 | | `nghttp2-debugsource` | Red Hat:rhel_eus:8.1::crb | All versions | 0:1.33.0-3.el8_1.1 | | `httpd24-libnghttp2` | Red Hat:rhel_software_collections:3::el6 | All versions | 0:1.7.1-8.el6.1 | | `httpd24-libnghttp2-devel` | Red Hat:rhel_software_collections:3::el6 | All versions | 0:1.7.1-8.el6.1 | | `httpd24-nghttp2` | Red Hat:rhel_software_collections:3::el6 | All versions | 0:1.7.1-8.el6.1 | | `httpd24-nghttp2-debuginfo` | Red Hat:rhel_software_collections:3::el6 | All versions | 0:1.7.1-8.el6.1 | | `httpd24-libnghttp2` | Red Hat:rhel_software_collections:3::el7 | All versions | 0:1.7.1-8.el7.1 | | `httpd24-libnghttp2-devel` | Red Hat:rhel_software_collections:3::el7 | All versions | 0:1.7.1-8.el7.1 | | `httpd24-nghttp2` | Red Hat:rhel_software_collections:3::el7 | All versions | 0:1.7.1-8.el7.1 | | `httpd24-nghttp2-debuginfo` | Red Hat:rhel_software_collections:3::el7 | All versions | 0:1.7.1-8.el7.1 | | `servicemesh-proxy` | Red Hat:service_mesh:1.0::el8 | All versions | 0:1.0.10-3.el8 | | `servicemesh-proxy` | Red Hat:service_mesh:1.1::el8 | All versions | 0:1.1.2-3.el8 | Products: Debian Debian Linux, Fedoraproject Fedora, Nghttp2 Nghttp2, Nodejs Node.js, Opensuse Leap, Oracle Banking Extensibility Workbench, Oracle Blockchain Platform, Oracle Enterprise Communications Broker, Oracle Graalvm, Oracle Mysql. ## How do I fix CVE-2020-11080? Upgrade node to a fixed version for your release line: 10.21.0, 12.18.0 or 14.4.1. ## Is CVE-2020-11080 being exploited? There is no known exploitation of CVE-2020-11080 in the wild and no public exploit code. ## Other vulnerabilities in Debian Debian Linux - [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild) - [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild) - [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild) - [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild) - [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-11080 and fix it if it is affected. What it is: CVE-2020-11080 is a low-severity denial of service vulnerability in Debian Debian Linux, published on 3 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2020-11080 in the wild and no public exploit code. Affected packages and fixed versions: - node (Bitnami): affected from 10.13.0; fixed in 10.21.0, 12.18.0, 14.4.1 - node-min (Bitnami): affected from 10.0.0; fixed in 10.12.1, 10.21.0, 12.12.1, 12.18.0, 14.4.1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2020-11080/ (Markdown: https://insights.sbomify.com/CVE-2020-11080/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-11080 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-11080 - OSV: https://osv.dev/vulnerability/CVE-2020-11080 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-11080/ Summaries are generated and may contain mistakes; the official description above is the record.