Skip to content
Noroxi
CVE-2024-22019· NVD / CVE Program· CNA hackerone

A vulnerability in Node.js HTTP servers allows an attacker to send a specially crafted HTTP request with chunked encoding, leading to resour

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 3.1% (FIRST EPSS); higher than 87.9% 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.*.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. 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

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.

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
Feb 19, 2024
Updated
Jun 17, 2026
EPSS
3.1% · 87th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 3.1%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.5
CNA · hackerone
7.5
agree

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

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
  • No public exploit code on record
  • A fix has been released

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

Follow CVE-2024-22019

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
nodejsnode.js
netappastra control center

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

Watch new CVEs for node.js

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

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • nodejs node.js18.0.0 and later · before 18.19.1
  • nodejs node.js20.0.0 and later · before 20.11.1
  • nodejs node.js21.0.0 and later · before 21.6.2

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.11.1-1.module_el8.9.0+3775+d8460d351:20.11.1-1.module_el8.9.0+3775+d8460d35
AlmaLinux:8nodejsbefore 1:18.19.1-1.module_el8.9.0+3753+4de0891b1:18.19.1-1.module_el8.9.0+3753+4de0891b
AlmaLinux:8nodejsbefore 1:16.20.2-4.module_el8.9.0+3747+ead8229c1:16.20.2-4.module_el8.9.0+3747+ead8229c
AlmaLinux:8nodejs-develbefore 1:16.20.2-4.module_el8.9.0+3747+ead8229c1:16.20.2-4.module_el8.9.0+3747+ead8229c
AlmaLinux:8nodejs-develbefore 1:20.11.1-1.module_el8.9.0+3775+d8460d351:20.11.1-1.module_el8.9.0+3775+d8460d35
AlmaLinux:8nodejs-develbefore 1:18.19.1-1.module_el8.9.0+3753+4de0891b1:18.19.1-1.module_el8.9.0+3753+4de0891b
AlmaLinux:8nodejs-docsbefore 1:20.11.1-1.module_el8.9.0+3775+d8460d351:20.11.1-1.module_el8.9.0+3775+d8460d35
AlmaLinux:8nodejs-docsbefore 1:18.19.1-1.module_el8.9.0+3753+4de0891b1:18.19.1-1.module_el8.9.0+3753+4de0891b
AlmaLinux:8nodejs-docsbefore 1:16.20.2-4.module_el8.9.0+3747+ead8229c1:16.20.2-4.module_el8.9.0+3747+ead8229c
AlmaLinux:8nodejs-full-i18nbefore 1:16.20.2-4.module_el8.9.0+3747+ead8229c1:16.20.2-4.module_el8.9.0+3747+ead8229c
AlmaLinux:8nodejs-full-i18nbefore 1:18.19.1-1.module_el8.9.0+3753+4de0891b1:18.19.1-1.module_el8.9.0+3753+4de0891b
AlmaLinux:8nodejs-full-i18nbefore 1:20.11.1-1.module_el8.9.0+3775+d8460d351:20.11.1-1.module_el8.9.0+3775+d8460d35
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.8.0+3614+204d6f433.0.1-1.module_el8.8.0+3614+204d6f43
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.7.0+3343+ea2b79012021.06-4.module_el8.7.0+3343+ea2b7901
AlmaLinux:8nodejs-packagingbefore 26-1.module_el8.8.0+3614+204d6f4326-1.module_el8.8.0+3614+204d6f43
AlmaLinux:8nodejs-packagingbefore 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.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.2.4-1.20.11.1.1.module_el8.9.0+3775+d8460d351:10.2.4-1.20.11.1.1.module_el8.9.0+3775+d8460d35
AlmaLinux:8npmbefore 1:8.19.4-1.16.20.2.4.module_el8.9.0+3747+ead8229c1:8.19.4-1.16.20.2.4.module_el8.9.0+3747+ead8229c
AlmaLinux:8npmbefore 1:10.2.4-1.18.19.1.1.module_el8.9.0+3753+4de0891b1:10.2.4-1.18.19.1.1.module_el8.9.0+3753+4de0891b
AlmaLinux:9nodejsbefore 1:16.20.2-4.el9_31:16.20.2-4.el9_3

+96

Same product

nodejs: all records

Other highest-scoring records for the same primary product.

  • CVE-2019-15605HTTP request smuggling in Node.js 10, 12, and 13 causes malicious payload delivery when transfer-encoding is malformed
    56Plan
  • CVE-2021-22883Node.js before 10.24.0, 12.21.0, 14.16.0, and 15.10.0 is vulnerable to a denial of service attack when too many connection attempts with an
    53Plan
  • CVE-2021-22930Node.js before 16.6.0, 14.17.4, and 12.22.4 is vulnerable to a use after free attack where an attacker might be able to exploit the memory c
    50Plan

Published before and after this one in the same product

  • ← EarlierCVE-2024-21891Feb 19, 2024 · Node.js depends on multiple built-in utility functions to normalize paths provided to node:fs functions, which can be overwitten with user-d
    35Monitor
  • ← EarlierCVE-2024-21896Feb 19, 2024 · The permission model protects itself against path traversal attacks by calling path.resolve() on any paths given by the user.
    39Monitor
  • Later →CVE-2025-23084Jan 28, 2025 · A vulnerability has been identified in Node.js, specifically affecting the handling of drive names in the Windows environment.
    22Monitor

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.19.1Vendor (CNA)
NodeJS Node19.*Vendor (CNA)
NodeJS Node20.11.1Vendor (CNA)
NodeJS Node21.6.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:16.20.2-4.el9_3 · AlmaLinux:9Package registry (OSV)
almalinux:nodejs-devel1:16.20.2-4.module_el8.9.0+3747+ead8229c · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-docs1:16.20.2-4.el9_3 · AlmaLinux:9Package registry (OSV)
almalinux:nodejs-full-i18n1:16.20.2-4.el9_3 · AlmaLinux:9Package registry (OSV)
almalinux:nodejs-libs1:16.20.2-4.el9_3 · AlmaLinux:9Package registry (OSV)
almalinux:nodejs-nodemon3.0.1-1.module_el8.8.0+3614+204d6f43 · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-packaging26-1.module_el8.8.0+3614+204d6f43 · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-packaging-bundler2021.06-4.module_el9.1.0+13+d9a595ea · AlmaLinux:9Package registry (OSV)
almalinux:npm1:8.19.4-1.16.20.2.4.el9_3 · AlmaLinux:9Package registry (OSV)
debian:nodejs18.20.4+dfsg-1~deb12u1 · Debian:12Package registry (OSV)
opensuse:nodejs1818.19.1-150400.9.18.2 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:nodejs2020.11.1-150500.11.6.1 · openSUSE:Leap 15.5Package registry (OSV)

+22

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

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.

No dated events beyond publication.

EPSS, last 120 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.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

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
none
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
None
Availability impact
High

Weakness class (CWE)

CWE-404 · Improper Resource Shutdown or Release

CVSS vector

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

nvd-primary

Attack context

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

Change log

  1. Exploit maturitypoc → none
  2. Fix✗ → ✓

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

References

Show all references (3 more)

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

All records