Node.js: All versions prior to Node.js 6.15.0, 8.14.0, 10.14.0 and 11.3.0: Slowloris HTTP Denial of Service: An attacker can cause a Denial
Node.js: All versions prior to Node.js 6.15.0, 8.14.0, 10.14.0 and 11.3.0: Slowloris HTTP Denial of Service: An attacker can cause a Denial of Service (DoS) by sending headers very slowly keeping HTTP or HTTPS connections and associated resources alive for a long period of time.
- Published
- Nov 28, 2018
- Updated
- Jun 16, 2026
- EPSS
- 41.3% · 99th percentile
- CWE
- CWE-400
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
42
Plan
Add it to your regular patch cycle.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 12 / 30 · 41.3%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| nodejs | node.js | cpe:2.3:a:nodejs:node.js |
| suse | suse enterprise storage | cpe:2.3:a:suse:suse_enterprise_storage |
| suse | suse linux enterprise server | cpe:2.3:o:suse:suse_linux_enterprise_server |
| suse | suse openstack cloud | cpe:2.3:o:suse:suse_openstack_cloud |
Using node.js? Add it to your stack and be the first to know about CVEs like this one. (Node.js)
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- nodejs node.js6.0.0 and later · before 6.15.1
- nodejs node.js8.0.0 and later · before 8.14.0
- nodejs node.js10.0.0 and later · before 10.14.0
- nodejs node.js11.0.0 and later · before 11.3.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (nodejs). Independent of NVD's CPE analysis and usually ahead of it.
The Node.js Project Node.js
- All versions prior to Node.js 6.15.0, 8.14.0, 10.14.0 and 11.3.0affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | nodejs | before 10.14.0-r0 | 10.14.0-r0 |
| Alpine:v3.8 | nodejs | before 8.14.0-r0 | 8.14.0-r0 |
| Debian:12 | nodejs | before 10.15.0~dfsg-6 | 10.15.0~dfsg-6 |
| openSUSE:Leap 15.0 | nodejs8 | before 8.15.0-lp150.2.9.1 | 8.15.0-lp150.2.9.1 |
| Red Hat:rhel_software_collections:3::el7 | rh-nodejs10 | before 0:3.2-3.el7 | 0:3.2-3.el7 |
| Red Hat:rhel_software_collections:3::el7 | rh-nodejs10-nodejs | before 0:10.16.3-3.el7 | 0:10.16.3-3.el7 |
| Red Hat:rhel_software_collections:3::el7 | rh-nodejs10-nodejs-debuginfo | before 0:10.16.3-3.el7 | 0:10.16.3-3.el7 |
| Red Hat:rhel_software_collections:3::el7 | rh-nodejs10-nodejs-devel | before 0:10.16.3-3.el7 | 0:10.16.3-3.el7 |
| Red Hat:rhel_software_collections:3::el7 | rh-nodejs10-nodejs-docs | before 0:10.16.3-3.el7 | 0:10.16.3-3.el7 |
| Red Hat:rhel_software_collections:3::el7 | rh-nodejs10-npm | before 0:6.9.0-10.16.3.3.el7 | 0:6.9.0-10.16.3.3.el7 |
| Red Hat:rhel_software_collections:3::el7 | rh-nodejs10-runtime | before 0:3.2-3.el7 | 0:3.2-3.el7 |
| Red Hat:rhel_software_collections:3::el7 | rh-nodejs10-scldevel | before 0:3.2-3.el7 | 0:3.2-3.el7 |
| Red Hat:rhel_software_collections:3::el7 | rh-nodejs8-nodejs | before 0:8.16.0-1.el7 | 0:8.16.0-1.el7 |
| Red Hat:rhel_software_collections:3::el7 | rh-nodejs8-nodejs-debuginfo | before 0:8.16.0-1.el7 | 0:8.16.0-1.el7 |
| Red Hat:rhel_software_collections:3::el7 | rh-nodejs8-nodejs-devel | before 0:8.16.0-1.el7 | 0:8.16.0-1.el7 |
| Red Hat:rhel_software_collections:3::el7 | rh-nodejs8-nodejs-docs | before 0:8.16.0-1.el7 | 0:8.16.0-1.el7 |
| Red Hat:rhel_software_collections:3::el7 | rh-nodejs8-npm | before 0:6.4.1-8.16.0.1.el7 | 0:6.4.1-8.16.0.1.el7 |
| SUSE:Linux Enterprise Module for Web and Scripting 12 | nodejs4 | before 4.9.1-15.17.1 | 4.9.1-15.17.1 |
| SUSE:Linux Enterprise Module for Web and Scripting 15 | nodejs8 | before 8.15.0-3.11.1 | 8.15.0-3.11.1 |
| SUSE:OpenStack Cloud 7 | nodejs6 | before 6.16.0-11.21.1 | 6.16.0-11.21.1 |
Same product
nodejs: all recordsOther 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 malformed56Plan
- 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 52Plan
- 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 c50Plan
- CVE-2021-22931Node.js before 16.6.0, 14.17.4, and 12.22.4 is vulnerable to Remote Code Execution, XSS, Application crashes due to missing input validation46Plan
- CVE-2020-8277A Node.js application that allows an attacker to trigger a DNS request for a host of their choice could trigger a Denial of Service in versi46Plan
- CVE-2017-14849Node.js 8.5.0 before 8.6.0 allows remote attackers to access unintended files, because a change to ".." handling was incompatible with the p46Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:nodejs | 10.14.0-r0 · Alpine:v3.10 | Package registry (OSV) |
| debian:nodejs | 10.15.0~dfsg-6 · Debian:12 | Package registry (OSV) |
| opensuse:nodejs8 | 8.15.0-lp150.2.9.1 · openSUSE:Leap 15.0 | Package registry (OSV) |
| red hat:rh-nodejs10 | 0:3.2-3.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs10-nodejs | 0:10.16.3-3.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs10-nodejs-debuginfo | 0:10.16.3-3.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs10-nodejs-devel | 0:10.16.3-3.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs10-nodejs-docs | 0:10.16.3-3.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs10-npm | 0:6.9.0-10.16.3.3.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs10-runtime | 0:3.2-3.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs8-nodejs | 0:8.16.0-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs8-nodejs-debuginfo | 0:8.16.0-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs8-nodejs-devel | 0:8.16.0-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs8-nodejs-docs | 0:8.16.0-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs8-npm | 0:6.4.1-8.16.0.1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| suse:nodejs4 | 4.9.1-15.17.1 · SUSE:Linux Enterprise Module for Web and Scripting 12 | Package registry (OSV) |
| suse:nodejs6 | 6.16.0-11.21.1 · SUSE:OpenStack Cloud 7 | Package registry (OSV) |
| suse:nodejs8 | 8.15.0-3.11.1 · SUSE:Linux Enterprise Module for Web and Scripting 15 | Package registry (OSV) |
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.
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 researchersFinders, 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
- 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-400 · Uncontrolled Resource ConsumptionCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Root cause
Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.
The bug in code
The whole CWE-400 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
function expand(node) { return node.children.map(expand);}Fixed
const MAX_DEPTH = 32;function expand(node, depth = 0) { if (depth > MAX_DEPTH) throw new Error("too deep"); return node.children.map((c) => expand(c, depth + 1));}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- www.securityfocus.com/bid/106043
- access.redhat.com/errata/RHSA-2019:1821
- nodejs.org/en/blog/vulnerability/november-2018-security-releases/
- security.gentoo.org/glsa/202003-48
- security.netapp.com/advisory/ntap-20241213-0009/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.