CVE-2024-27983
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 · uneditedAn attacker can make the Node.js HTTP/2 server completely unavailable by sending a small amount of HTTP/2 frames packets with a few HTTP/2 frames inside. It is possible to leave some data in nghttp2 memory after reset when headers with HTTP/2 CONTINUATION frame are sent to the server and then a TCP connection is abruptly closed by the client triggering the Http2Session destructor while header frames are still being processed (and stored in memory) causing a race condition.
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 · moderate confidenceAn attacker can render a Node.js HTTP/2 server completely unavailable by sending specially crafted HTTP/2 frames containing CONTINUATION frames followed by an abrupt TCP connection closure. This triggers a race condition in the Http2Session destructor where header frames remain in memory during processing, causing the server to crash or become unresponsive.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Low
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 Node.js version numberAffected if The installed version falls within the range of versions known to be vulnerable to this HTTP/2 race condition flaw
-
Determine if HTTP/2 is in useInspect application code or server configuration for use of the Node.js 'http2' module, or check if the server exposes HTTP/2 endpoints (listen on h2 protocol)Affected if HTTP/2 is enabled and the server accepts HTTP/2 connections on any endpoint
-
Check for exposed HTTP/2 server configurationsReview any Node.js server scripts that create Http2Server instances or use the 'http2' module with 'createServer()' or 'createSecureServer()'Affected if The application creates HTTP/2 servers or uses HTTP/2 multiplexing features
-
Inspect reverse proxy or load balancer HTTP/2 settingsIf Node.js sits behind a proxy (nginx, HAProxy, etc.), check whether HTTP/2 pass-through or upgrade is configuredAffected if HTTP/2 traffic is being forwarded to the Node.js backend server
-
Verify network exposure of HTTP/2 serviceScan listening ports or review firewall rules to confirm HTTP/2 services are reachable from untrusted networksAffected if The HTTP/2 service is exposed to the internet or untrusted users who could send malicious CONTINUATION frames
A user is affected if they run a vulnerable Node.js version with HTTP/2 enabled and exposed, where remote attackers can send specially crafted HTTP/2 CONTINUATION frames followed by abrupt TCP closure to trigger the race condition.
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.
From vendor dataUpgrade Node.js to a version that addresses this vulnerability; if immediate patching is not feasible, consider disabling HTTP/2 or implementing upstream rate limiting and connection controls at a reverse proxy.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-27983 — 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-27983 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