Skip to content
Noroxi
NVD / CVE Program· CNA hackerone

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 with a few HTTP/2 f

Noroxi assessment

Priority: Plan (action score 57/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 84.3% (FIRST EPSS); higher than 99.7% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: NodeJS Node 10.*, 11.*, 12.*.

Add it to your regular patch cycle. Upgrade to NodeJS Node 10.*, 11.*, 12.* or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 8.2 · v3.0—Proof of concept Fix available
Published
Apr 8, 2024
Updated
Jun 17, 2026
EPSS
84.3% · 99th percentile

Report tools

JSON

Action score

57

Plan

Add it to your regular patch cycle.

CVSS
32 / 40 · 8.2 / 10
CISA KEV
0 / 30 · Not listed
EPSS
25 / 30 · 84.3%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · hackerone
8.2
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-27983

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for nodejs records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
nodejsnodejs

Using node? Add it to your stack and be the first to know about CVEs like this one. (Node.js)

Watch new CVEs for node

When you'll hear from us

  • when a new CVE affecting this product is published
  • when a record in your stack enters KEV or gets exploit code

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every Monday

Versions reported by the vendor

Affected version ranges reported by the assigning authority (hackerone). Independent of NVD's CPE analysis and usually ahead of it.

  • NodeJS Node

    • 4.0 and later · before 4.*affected · semver
    • 5.0 and later · before 5.*affected · semver
    • 6.0 and later · before 6.*affected · semver
    • 7.0 and later · before 7.*affected · semver
    • 8.0 and later · before 8.*affected · semver
    • 9.0 and later · before 9.*affected · semver
    • 10.0 and later · before 10.*affected · semver
    • 11.0 and later · before 11.*affected · semver
    • 12.0 and later · before 12.*affected · semver
    • 13.0 and later · before 13.*affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8nodejsbefore 1:20.12.2-2.module_el8.9.0+3827+11b91f3e1:20.12.2-2.module_el8.9.0+3827+11b91f3e
AlmaLinux:8nodejsbefore 1:18.20.2-1.module_el8.9.0+3828+c9fa96441:18.20.2-1.module_el8.9.0+3828+c9fa9644
AlmaLinux:8nodejs-develbefore 1:20.12.2-2.module_el8.9.0+3827+11b91f3e1:20.12.2-2.module_el8.9.0+3827+11b91f3e
AlmaLinux:8nodejs-develbefore 1:18.20.2-1.module_el8.9.0+3828+c9fa96441:18.20.2-1.module_el8.9.0+3828+c9fa9644
AlmaLinux:8nodejs-docsbefore 1:18.20.2-1.module_el8.9.0+3828+c9fa96441:18.20.2-1.module_el8.9.0+3828+c9fa9644
AlmaLinux:8nodejs-docsbefore 1:20.12.2-2.module_el8.9.0+3827+11b91f3e1:20.12.2-2.module_el8.9.0+3827+11b91f3e
AlmaLinux:8nodejs-full-i18nbefore 1:18.20.2-1.module_el8.9.0+3828+c9fa96441:18.20.2-1.module_el8.9.0+3828+c9fa9644
AlmaLinux:8nodejs-full-i18nbefore 1:20.12.2-2.module_el8.9.0+3827+11b91f3e1:20.12.2-2.module_el8.9.0+3827+11b91f3e
AlmaLinux:8nodejs-nodemonbefore 3.0.1-1.module_el8.8.0+3613+1ed8c91d3.0.1-1.module_el8.8.0+3613+1ed8c91d
AlmaLinux:8nodejs-nodemonbefore 3.0.1-1.module_el8.9.0+3731+490e3ce53.0.1-1.module_el8.9.0+3731+490e3ce5
AlmaLinux:8nodejs-packagingbefore 2021.06-4.module_el8.9.0+3684+11b9e9592021.06-4.module_el8.9.0+3684+11b9e959
AlmaLinux:8nodejs-packagingbefore 2021.06-4.module_el8.7.0+3343+ea2b79012021.06-4.module_el8.7.0+3343+ea2b7901
AlmaLinux:8nodejs-packaging-bundlerbefore 2021.06-4.module_el8.9.0+3684+11b9e9592021.06-4.module_el8.9.0+3684+11b9e959
AlmaLinux:8nodejs-packaging-bundlerbefore 2021.06-4.module_el8.7.0+3343+ea2b79012021.06-4.module_el8.7.0+3343+ea2b7901
AlmaLinux:8npmbefore 1:10.5.0-1.20.12.2.2.module_el8.9.0+3827+11b91f3e1:10.5.0-1.20.12.2.2.module_el8.9.0+3827+11b91f3e
AlmaLinux:8npmbefore 1:10.5.0-1.18.20.2.1.module_el8.9.0+3828+c9fa96441:10.5.0-1.18.20.2.1.module_el8.9.0+3828+c9fa9644
AlmaLinux:9nodejsbefore 1:20.12.2-2.module_el9.4.0+100+71fc95281:20.12.2-2.module_el9.4.0+100+71fc9528
AlmaLinux:9nodejsbefore 1:18.20.2-2.module_el9.4.0+99+a01f76761:18.20.2-2.module_el9.4.0+99+a01f7676
AlmaLinux:9nodejsbefore 1:16.20.2-8.el9_41:16.20.2-8.el9_4
AlmaLinux:9nodejs-develbefore 1:20.12.2-2.module_el9.4.0+100+71fc95281:20.12.2-2.module_el9.4.0+100+71fc9528
AlmaLinux:9nodejs-develbefore 1:18.20.2-2.module_el9.4.0+99+a01f76761:18.20.2-2.module_el9.4.0+99+a01f7676
AlmaLinux:9nodejs-docsbefore 1:18.20.2-2.module_el9.4.0+99+a01f76761:18.20.2-2.module_el9.4.0+99+a01f7676
AlmaLinux:9nodejs-docsbefore 1:20.12.2-2.module_el9.4.0+100+71fc95281:20.12.2-2.module_el9.4.0+100+71fc9528
AlmaLinux:9nodejs-docsbefore 1:16.20.2-8.el9_41:16.20.2-8.el9_4

+96

Same product

nodejs: all records

Other highest-scoring records for the same primary product.

  • CVE-2025-27210An incomplete fix has been identified for CVE-2025-23084 in Node.js, specifically affecting Windows device names like CON, PRN, and AUX.
    34Monitor
  • CVE-2024-27980Due to the improper handling of batch files in child_process.spawn / child_process.spawnSync, a malicious command line argument can inject a
    32Monitor
  • CVE-2024-36138Bypass incomplete fix of CVE-2024-27980, that arises from improper handling of batch files with all possible extensions on Windows via child
    32Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2024-22017Mar 19, 2024 · setuid() does not affect libuv's internal io_uring operations if initialized before the call to setuid().
    29Monitor
  • ← EarlierCVE-2024-22025Mar 19, 2024 · A vulnerability in Node.js has been identified, allowing for a Denial of Service (DoS) attack through resource exhaustion when using the fet
    26Monitor
  • Later →CVE-2024-27982May 7, 2024 · The team has identified a critical vulnerability in the http server of the most recent version of Node, where malformed headers can lead to
    26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
NodeJS Node10.*Vendor (CNA)
NodeJS Node11.*Vendor (CNA)
NodeJS Node12.*Vendor (CNA)
NodeJS Node13.*Vendor (CNA)
NodeJS Node14.*Vendor (CNA)
NodeJS Node15.*Vendor (CNA)
NodeJS Node16.*Vendor (CNA)
NodeJS Node17.*Vendor (CNA)
NodeJS Node18.20.1Vendor (CNA)
NodeJS Node19.*Vendor (CNA)
NodeJS Node20.12.1Vendor (CNA)
NodeJS Node21.7.2Vendor (CNA)
NodeJS Node4.*Vendor (CNA)
NodeJS Node5.*Vendor (CNA)
NodeJS Node6.*Vendor (CNA)
NodeJS Node7.*Vendor (CNA)
NodeJS Node8.*Vendor (CNA)
NodeJS Node9.*Vendor (CNA)
almalinux:nodejs1:20.12.2-2.module_el8.9.0+3827+11b91f3e · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-devel1:20.12.2-2.module_el8.9.0+3827+11b91f3e · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-docs1:20.12.2-2.module_el8.9.0+3827+11b91f3e · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-full-i18n1:20.12.2-2.module_el8.9.0+3827+11b91f3e · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-libs1:16.20.2-8.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:nodejs-nodemon3.0.1-1.module_el8.9.0+3731+490e3ce5 · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-packaging2021.06-4.module_el8.9.0+3684+11b9e959 · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-packaging-bundler2021.06-4.module_el8.9.0+3684+11b9e959 · AlmaLinux:8Package registry (OSV)
almalinux:npm1:10.5.0-1.20.12.2.2.module_el8.9.0+3827+11b91f3e · AlmaLinux:8Package registry (OSV)
alpine:nodejs18.20.1-r0 · Alpine:v3.17Package registry (OSV)
alpine:nodejs-current21.7.2-r0 · Alpine:v3.19Package registry (OSV)
debian:nodejs18.20.4+dfsg-1~deb12u1 · Debian:12Package registry (OSV)

+24

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:72024-04-14

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+5 d
  3. TodayNov 10, 2026+946 d
EPSS, last 120 days-3% in 7 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
low · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
Low
Availability impact
High

Weakness class (CWE)

CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

CVSS vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records