# CVE-2024-22019: Denial of service in Node > Attackers can cause denial of service in Node.js HTTP servers by sending crafted chunked requests that exhaust resources, bypassing standard limits. - **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 20 Feb 2024 - **Updated:** 4 Nov 2025 - **Also known as:** ALSA-2024:1438, AZL-34461, AZL-35047, BELL-CVE-2024-22019, BIT-node-2024-22019, BIT-node-min-2024-22019, CLSA-2025-1754412086, DEBIAN-CVE-2024-22019, GHSA-prhj-8562-p8gj, RHSA-2024:1354, RHSA-2024:1424, RHSA-2024:1438, RHSA-2024:1678, RHSA-2024:2651, RHSA-2024:2793, RLSA-2024:1438 ## What is CVE-2024-22019? CVE-2024-22019 is a high-severity denial of service vulnerability in Nodejs Node.js, published on 20 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description A vulnerability in Node.js HTTP servers allows an attacker to send a specially crafted HTTP request with chunked encoding, leading to resource exhaustion and denial of service (DoS). The server reads an unbounded number of bytes from a single connection, exploiting the lack of limitations on chunk extension bytes. The issue can cause CPU and network bandwidth exhaustion, bypassing standard safeguards like timeouts and body size limits. Weakness: CWE-404 (Improper Resource Shutdown or Release) ## Which versions are affected by CVE-2024-22019? 2 open source packages ship an affected version, including node and node-min. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `node` | Bitnami | All versions | 18.19.1, 20.11.1, 21.6.2 | | `node-min` | Bitnami | All versions | 18.19.1, 20.11.1, 21.6.2 | | `nodejs` | AlmaLinux:9 | All versions | 1:16.20.2-4.el9_3 | | `nodejs-docs` | AlmaLinux:9 | All versions | 1:16.20.2-4.el9_3 | | `nodejs-full-i18n` | AlmaLinux:9 | All versions | 1:16.20.2-4.el9_3 | | `nodejs-libs` | AlmaLinux:9 | All versions | 1:16.20.2-4.el9_3 | | `npm` | AlmaLinux:9 | All versions | 1:8.19.4-1.16.20.2.4.el9_3 | | `nodejs` | Red Hat:enterprise_linux:9::appstream | All versions | 1:16.20.2-4.el9_3 | | `nodejs-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 1:16.20.2-4.el9_3 | | `nodejs-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 1:16.20.2-4.el9_3 | | `nodejs-docs` | Red Hat:enterprise_linux:9::appstream | All versions | 1:16.20.2-4.el9_3 | | `nodejs-full-i18n` | Red Hat:enterprise_linux:9::appstream | All versions | 1:16.20.2-4.el9_3 | | `nodejs-libs` | Red Hat:enterprise_linux:9::appstream | All versions | 1:16.20.2-4.el9_3 | | `nodejs-libs-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 1:16.20.2-4.el9_3 | | `npm` | Red Hat:enterprise_linux:9::appstream | All versions | 1:8.19.4-1.16.20.2.4.el9_3 | | `nodejs` | Red Hat:rhel_eus:8.6::appstream | All versions | 1:16.20.2-4.module+el8.6.0+21547+94389150 | | `nodejs-debuginfo` | Red Hat:rhel_eus:8.6::appstream | All versions | 1:16.20.2-4.module+el8.6.0+21547+94389150 | | `nodejs-debugsource` | Red Hat:rhel_eus:8.6::appstream | All versions | 1:16.20.2-4.module+el8.6.0+21547+94389150 | | `nodejs-devel` | Red Hat:rhel_eus:8.6::appstream | All versions | 1:16.20.2-4.module+el8.6.0+21547+94389150 | | `nodejs-docs` | Red Hat:rhel_eus:8.6::appstream | All versions | 1:16.20.2-4.module+el8.6.0+21547+94389150 | | `nodejs-full-i18n` | Red Hat:rhel_eus:8.6::appstream | All versions | 1:16.20.2-4.module+el8.6.0+21547+94389150 | | `nodejs-nodemon` | Red Hat:rhel_eus:8.6::appstream | All versions | 0:3.0.1-1.module+el8.6.0+19765+366b9144 | | `nodejs-packaging` | Red Hat:rhel_eus:8.6::appstream | All versions | 0:26-1.module+el8.6.0+19856+c0c87259 | | `npm` | Red Hat:rhel_eus:8.6::appstream | All versions | 1:8.19.4-1.16.20.2.4.module+el8.6.0+21547+94389150 | | `nodejs` | Red Hat:rhel_eus:8.8::appstream | All versions | 1:16.20.2-4.module+el8.8.0+21546+ecd4bb56 | | `nodejs-debuginfo` | Red Hat:rhel_eus:8.8::appstream | All versions | 1:16.20.2-4.module+el8.8.0+21546+ecd4bb56 | | `nodejs-debugsource` | Red Hat:rhel_eus:8.8::appstream | All versions | 1:16.20.2-4.module+el8.8.0+21546+ecd4bb56 | | `nodejs-devel` | Red Hat:rhel_eus:8.8::appstream | All versions | 1:16.20.2-4.module+el8.8.0+21546+ecd4bb56 | | `nodejs-docs` | Red Hat:rhel_eus:8.8::appstream | All versions | 1:16.20.2-4.module+el8.8.0+21546+ecd4bb56 | | `nodejs-full-i18n` | Red Hat:rhel_eus:8.8::appstream | All versions | 1:16.20.2-4.module+el8.8.0+21546+ecd4bb56 | | `nodejs-nodemon` | Red Hat:rhel_eus:8.8::appstream | All versions | 0:3.0.1-1.module+el8.8.0+19764+7eed1ca3 | | `nodejs-packaging` | Red Hat:rhel_eus:8.8::appstream | All versions | 0:26-1.module+el8.8.0+19857+6d2a104d | | `npm` | Red Hat:rhel_eus:8.8::appstream | All versions | 1:8.19.4-1.16.20.2.4.module+el8.8.0+21546+ecd4bb56 | | `nodejs` | Red Hat:rhel_eus:9.0::appstream | All versions | 1:16.20.2-4.el9_0 | | `nodejs-debuginfo` | Red Hat:rhel_eus:9.0::appstream | All versions | 1:16.20.2-4.el9_0 | | `nodejs-debugsource` | Red Hat:rhel_eus:9.0::appstream | All versions | 1:16.20.2-4.el9_0 | | `nodejs-docs` | Red Hat:rhel_eus:9.0::appstream | All versions | 1:16.20.2-4.el9_0 | | `nodejs-full-i18n` | Red Hat:rhel_eus:9.0::appstream | All versions | 1:16.20.2-4.el9_0 | | `nodejs-libs` | Red Hat:rhel_eus:9.0::appstream | All versions | 1:16.20.2-4.el9_0 | | `nodejs-libs-debuginfo` | Red Hat:rhel_eus:9.0::appstream | All versions | 1:16.20.2-4.el9_0 | Products: Netapp Astra Control Center, Nodejs Node.js. ## How do I fix CVE-2024-22019? Upgrade node to a fixed version for your release line: 18.19.1, 20.11.1 or 21.6.2. ## Is CVE-2024-22019 being exploited? There is no known exploitation of CVE-2024-22019 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-22019 and fix it if it is affected. What it is: CVE-2024-22019 is a high-severity denial of service vulnerability in Nodejs Node.js, published on 20 Feb 2024. 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-2024-22019 in the wild and no public exploit code. Affected packages and fixed versions: - node (Bitnami): affected all versions; fixed in 18.19.1, 20.11.1, 21.6.2 - node-min (Bitnami): affected all versions; fixed in 18.19.1, 20.11.1, 21.6.2 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-2024-22019/ (Markdown: https://insights.sbomify.com/CVE-2024-22019/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-22019 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-22019 - OSV: https://osv.dev/vulnerability/CVE-2024-22019 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-22019/ Summaries are generated and may contain mistakes; the official description above is the record.