Node.jsApplication
CVE-2024-22019
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a denial-of-service vulnerability in Node.js HTTP servers where specially crafted chunked encoding HTTP requests can cause unbounded reading of bytes. The lack of limitations on chunk extension bytes allows attackers to exhaust CPU and network resources from a single connection, bypassing standard safeguards like timeouts and body size limits.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Node.jsApplication
>= 18.0.0, < 18.19.1>= 20.0.0, < 20.11.1>= 21.0.0, < 21.6.2all versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Node.js installation and versionRun `node --version` to obtain the installed Node.js version. Compare this version against the affected ranges: 18.0.0 through <18.19.1, 20.0.0 through <20.11.1, and 21.0.0 through <21.6.2.Affected if The installed version falls within any of the affected version ranges.
-
Determine if Node.js is used as an HTTP serverReview application configurations, process listings, or startup scripts to identify whether Node.js is running an HTTP server (commonly using built-in http module, Express, Fastify, or similar frameworks).Affected if Node.js is running as an HTTP server and the version is affected.
-
Check for NetApp Astra Control Center deploymentIdentify any installed instances of NetApp Astra Control Center in the environment. This may be found via container listings, installed software inventories, or orchestration manifests.Affected if NetApp Astra Control Center is deployed, as all versions are affected regardless of Node.js version.
-
Verify HTTP server accepts chunked transfer encodingInspect the HTTP server configuration or application code to determine whether chunked transfer encoding is enabled or accepted for incoming requests. This is typically the default behavior in Node.js HTTP servers.Affected if The HTTP server accepts chunked encoding requests from clients.
A user is affected if they run a Node.js HTTP server with a version in the affected ranges (18.x before 18.19.1, 20.x before 20.11.1, or 21.x before 21.6.2) or if they have NetApp Astra Control Center deployed, and the server accepts chunked encoding requests.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped18.19.120.11.121.6.2
Apply available Node.js security patches/updates to fix the chunked encoding parsing. Additionally, implement connection-level timeouts and consider using reverse proxies with request size/connection limits as a defense-in-depth measure.
Node.js 18.19.1+ (LTS), 20.11.1+ (LTS), or 21.6.2+; contact NetApp for Astra Control Center
- Identify the current Node.js version by running 'node --version'
- For Node.js 18.x users: Upgrade to version 18.19.1 or later (e.g., using nvm: 'nvm install 18.19.1' then 'nvm use 18.19.1')
- For Node.js 20.x users: Upgrade to version 20.11.1 or later (e.g., using nvm: 'nvm install 20.11.1' then 'nvm use 20.11.1')
- For Node.js 21.x users: Upgrade to version 21.6.2 or later (e.g., using nvm: 'nvm install 21.6.2' then 'nvm use 21.6.2')
- Alternatively, use official Node.js installers from nodejs.org for your operating system
- Verify the upgrade was successful by running 'node --version'
- Restart any Node.js services or applications to ensure they use the new version
- For Astra Control Center: Contact NetApp support for specific patched versions as this product has no publicly disclosed fix version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Node.js
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-22019 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-22019 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data