Home/CVE/An attacker can make the Node.js HTTP/2 server completely unavailable by sending a small amount of HTTP/2 frames packets
CVE
CVE-2024-27983
An attacker can make the Node.js HTTP/2 server completely unavailable by sending a small amount of HTTP/2 frames packets
An 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.
HIGH · CVSS 8.2
EPSS 0.75933
Act now
- EPSS ≥ 0.50 - high probability of exploitation in the next 30 days
- EPSS percentile: top 1% of all CVEs by exploitation likelihood
- Public exploit or PoC is available
- SSVC automatable: yes - attacks can be scripted at scale
- CVSS base score ≥ 7.0
Sigma rules0
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2024-27983, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
◆
ATT&CK techniques
1Techniques this CVE enables - linked via CWECAPECATT&CK. High◆ = named directly in ATT&CK or Nuclei templates.
▤ Build a SIEM detection for these techniques▤
CAPEC attack patterns
2Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.
⬡
Weakness Classification
▤
Affected Packages
7Language-ecosystem packages (from OSV) tied to this CVE, with the version that fixes it - the dependency-level detail NVD doesn’t carry.
Debian:11
nodejs
fixed in 12.22.12~dfsg-1~deb11u5
Ubuntu:20.04:LTS
nodejs
Ubuntu:22.04:LTS
nodejs
Ubuntu:24.04:LTS
nodejs
Ubuntu:Pro:14.04:LTS
nodejs
Ubuntu:Pro:16.04:LTS
nodejs
Ubuntu:Pro:18.04:LTS
nodejs
⚠
Public Exploits & PoCs
12These PoC and exploit links come from public sources and are not verified to be safe or functional. Review the code before running anything, and treat unverified entries as untrusted.
📦
Fixed versions by distribution
60The package version that resolves this CVE on each Linux distribution, from the vendor’s published security data. fixed in shows a patched version exists; open means the package is listed as affected with no fix yet.
alpine edgenodejs fixed in 20.12.1-r0
alpine edgenodejs-current fixed in 21.7.2-r0
alpine v3.19nodejs fixed in 20.12.1-r0
alpine v3.19nodejs-current fixed in 21.7.2-r0
alpine v3.20nodejs fixed in 20.12.1-r0
alpine v3.20nodejs-current fixed in 21.7.2-r0
oracle allnodejs open
oracle allnodejs-devel fixed in 1:18.20.2-1.module+el8.9.0+90319+0b1e7189
oracle allnodejs-docs fixed in 1:18.20.2-1.module+el8.9.0+90319+0b1e7189
oracle allnodejs-full-i18n fixed in 1:18.20.2-1.module+el8.9.0+90319+0b1e7189
oracle allnodejs-libs open
oracle allnodejs-nodemon open
oracle allnodejs-packaging open
oracle allnodejs-packaging-bundler fixed in 0:2021.06-4.module+el8.9.0+90157+ed89dc20
oracle allnpm open
rhel 8nodejs open
rhel 8nodejs-devel fixed in 1:18.20.2-1.module+el8.9.0+21767+537f34ee
rhel 8nodejs-docs fixed in 1:18.20.2-1.module+el8.9.0+21767+537f34ee
rhel 8nodejs-full-i18n open
rhel 8nodejs-nodemon fixed in 0:3.0.1-1.module+el8.9.0+21190+5ebd2c33
rhel 8nodejs-packaging fixed in 0:2021.06-4.module+el8.9.0+21190+5ebd2c33
rhel 8nodejs-packaging-bundler fixed in 0:2021.06-4.module+el8.9.0+21190+5ebd2c33
rhel 8npm open
rhel 9nodejs fixed in 1:16.20.2-8.el9_4
rhel 9nodejs-devel fixed in 1:20.12.2-2.module+el9.4.0+21731+46b5b8a7
rhel 9nodejs-docs open
rhel 9nodejs-full-i18n fixed in 1:16.20.2-8.el9_4
rhel 9nodejs-libs open
rhel 9nodejs-nodemon fixed in 0:3.0.1-1.module+el9.3.0.z+20478+84a9f781
rhel 9nodejs-packaging open
rhel 9nodejs-packaging-bundler fixed in 0:2021.06-4.module+el9.3.0+19518+63aad52d
rhel 9npm fixed in 1:8.19.4-1.16.20.2.8.el9_4
suse sle15nodejs10 open
suse sle15nodejs10-devel open
suse sle15nodejs10-docs open
suse sle15nodejs12 fixed in 0:12.22.12-150200.4.59.1
suse sle15nodejs12-devel fixed in 0:12.22.12-150200.4.59.1
suse sle15nodejs12-docs fixed in 0:12.22.12-150200.4.59.1
suse sle15nodejs14 fixed in 0:14.21.3-150200.15.58.1
suse sle15nodejs14-devel fixed in 0:14.21.3-150200.15.58.1
suse sle15nodejs14-docs fixed in 0:14.21.3-150200.15.58.1
suse sle15nodejs16 fixed in 0:16.20.2-150300.7.36.2
suse sle15nodejs16-devel fixed in 0:16.20.2-150300.7.36.2
suse sle15nodejs16-docs fixed in 0:16.20.2-150300.7.36.2
suse sle15nodejs18 fixed in 0:18.20.1-150400.9.21.3
suse sle15nodejs18-devel fixed in 0:18.20.1-150400.9.21.3
suse sle15nodejs18-docs fixed in 0:18.20.1-150400.9.21.3
suse sle15nodejs20 fixed in 0:20.12.1-150500.11.9.2
suse sle15nodejs20-devel fixed in 0:20.12.1-150500.11.9.2
suse sle15nodejs20-docs fixed in 0:20.12.1-150500.11.9.2
suse sle15nodejs8 open
suse sle15nodejs8-devel open
suse sle15nodejs8-docs open
suse sle15npm10 open
suse sle15npm12 fixed in 0:12.22.12-150200.4.59.1
suse sle15npm14 fixed in 0:14.21.3-150200.15.58.1
suse sle15npm16 fixed in 0:16.20.2-150400.3.33.1
suse sle15npm18 fixed in 0:18.20.1-150400.9.21.3
suse sle15npm20 fixed in 0:20.12.1-150500.11.9.2
suse sle15npm8 open
▣
Scoring & Timeline
8.2
HIGH · CVSS v3.0 · [email protected]
Attack Vector
Network
Adjacent
Local
Physical
Attack Complexity
Low
High
Privileges Required
None
Low
High
User Interaction
None
Required
Scope
Unchanged
Changed
Confidentiality
None
Low
High
Integrity
None
Low
High
Availability
None
Low
High
SSVC triage · cisa-vulnrichment
Exploitation
none
Automatable
yes
Technical impact
partial
SSVC asks the questions that actually drive patch urgency: is it being exploited, can attacks be automated, and how total is the impact.
⚑
Vendor Advisories
26siemens-csafSSA-915275
suse-csafopenSUSE-SU-2024:13851-1
suse-csafopenSUSE-SU-2024:13852-1
suse-csafSUSE-SU-2024:1346-1
suse-csafSUSE-SU-2024:1355-1
🔗
References & Sources
7Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.