CVE-2019-5737: In Node.js including 6.x before 6.17.0, 8.x before 8.15.1, 10.x before 10.15.2, and 11.x before 11.10.1, an attacker can cause a Denial of S
Noroxi assessment
Priority: Monitor (action score 35/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: 16.1% (FIRST EPSS); higher than 96.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.
- Fixed version: nodejs (Alpine:v3.10) 10.15.3-r0; nodejs (Debian:12) 10.15.2~dfsg-1; nodejs (Red Hat:enterprise_linux:8::appstream) 1:10.16.3-2.module+el8.0.0+4214+49953fda.
Low priority for now. Upgrade to nodejs (Alpine:v3.10) 10.15.3-r0; nodejs (Debian:12) 10.15.2~dfsg-1; nodejs (Red Hat:enterprise_linux:8::appstream) 1:10.16.3-2.module+el8.0.0+4214+49953fda 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
In Node.js including 6.x before 6.17.0, 8.x before 8.15.1, 10.x before 10.15.2, and 11.x before 11.10.1, an attacker can cause a Denial of Service (DoS) by establishing an HTTP or HTTPS connection in keep-alive mode and by sending headers very slowly. This keeps the connection and associated resources alive for a long period of time. Potential attacks are mitigated by the use of a load balancer or other proxy layer. This vulnerability is an extension of CVE-2018-12121, addressed in November and impacts all active Node.js release lines including 6.x before 6.17.0, 8.x before 8.15.1, 10.x before 10.15.2, and 11.x before 11.10.1.
- Published
- Mar 28, 2019
- Updated
- Jun 16, 2026
- EPSS
- 16.1% · 96th percentile
- CWE
- CWE-400
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 5 / 30 · 16.1%
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
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.17.0
- nodejs node.js8.0.0 and later · before 8.15.1
- nodejs node.js10.0.0 and later · before 10.15.2
- nodejs node.js11.0.0 and later · before 11.10.1
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.
Node.js Node.js
- All versions prior to 6.17.0, All versions prior to 8.15.1, All versions prior to 10.15.2, All versions prior to 11.10.1affected
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.15.3-r0 | 10.15.3-r0 |
| Debian:12 | nodejs | before 10.15.2~dfsg-1 | 10.15.2~dfsg-1 |
| Red Hat:enterprise_linux:8::appstream | nodejs | before 1:10.16.3-2.module+el8.0.0+4214+49953fda | 1:10.16.3-2.module+el8.0.0+4214+49953fda |
| Red Hat:enterprise_linux:8::appstream | nodejs-debuginfo | before 1:10.16.3-2.module+el8.0.0+4214+49953fda | 1:10.16.3-2.module+el8.0.0+4214+49953fda |
| Red Hat:enterprise_linux:8::appstream | nodejs-debugsource | before 1:10.16.3-2.module+el8.0.0+4214+49953fda | 1:10.16.3-2.module+el8.0.0+4214+49953fda |
| Red Hat:enterprise_linux:8::appstream | nodejs-devel | before 1:10.16.3-2.module+el8.0.0+4214+49953fda | 1:10.16.3-2.module+el8.0.0+4214+49953fda |
| Red Hat:enterprise_linux:8::appstream | nodejs-devel-debuginfo | before 1:10.16.3-2.module+el8.0.0+4214+49953fda | 1:10.16.3-2.module+el8.0.0+4214+49953fda |
| Red Hat:enterprise_linux:8::appstream | nodejs-docs | before 1:10.16.3-2.module+el8.0.0+4214+49953fda | 1:10.16.3-2.module+el8.0.0+4214+49953fda |
| Red Hat:enterprise_linux:8::appstream | nodejs-nodemon | before 0:1.18.3-1.module+el8+2632+6c5111ed | 0:1.18.3-1.module+el8+2632+6c5111ed |
| Red Hat:enterprise_linux:8::appstream | nodejs-packaging | before 0:17-3.module+el8+2873+aa7dfd9a | 0:17-3.module+el8+2873+aa7dfd9a |
| Red Hat:enterprise_linux:8::appstream | npm | before 1:6.9.0-1.10.16.3.2.module+el8.0.0+4214+49953fda | 1:6.9.0-1.10.16.3.2.module+el8.0.0+4214+49953fda |
| 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 |
+6
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 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 c50Plan
Published before and after this one in the same product
- ← EarlierCVE-2018-12122Nov 28, 2018 · 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 42Plan
- ← EarlierCVE-2018-12123Nov 28, 2018 · Node.js: All versions prior to Node.js 6.15.0, 8.14.0, 10.14.0 and 11.3.0: Hostname spoofing in URL parser for javascript protocol: If a Nod18Monitor
- Later →CVE-2019-5739Mar 28, 2019 · Keep-alive HTTP and HTTPS connections can remain open and inactive for up to 2 minutes in Node.js 6.16.0 and earlier.31Monitor
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.15.3-r0 · Alpine:v3.10 | Package registry (OSV) |
| debian:nodejs | 10.15.2~dfsg-1 · Debian:12 | Package registry (OSV) |
| red hat:nodejs | 1:10.16.3-2.module+el8.0.0+4214+49953fda · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:nodejs-debuginfo | 1:10.16.3-2.module+el8.0.0+4214+49953fda · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:nodejs-debugsource | 1:10.16.3-2.module+el8.0.0+4214+49953fda · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:nodejs-devel | 1:10.16.3-2.module+el8.0.0+4214+49953fda · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:nodejs-devel-debuginfo | 1:10.16.3-2.module+el8.0.0+4214+49953fda · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:nodejs-docs | 1:10.16.3-2.module+el8.0.0+4214+49953fda · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:nodejs-nodemon | 0:1.18.3-1.module+el8+2632+6c5111ed · Red Hat:enterprise_linux:8::appstream | 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) |
| rocky linux:nodejs-nodemon | 0:1.18.3-1.module+el8.3.0+101+f84c7154 · Rocky Linux:8 | Package registry (OSV) |
| rocky linux:nodejs-packaging | 0:17-3.module+el8.3.0+101+f84c7154 · Rocky Linux:8 | Package registry (OSV) |
| suse:nodejs10 | 10.15.2-1.6.1 · SUSE:Linux Enterprise Module for Web and Scripting 15 | Package registry (OSV) |
| suse:nodejs4 | 4.9.1-15.20.1 · SUSE:Linux Enterprise Module for Web and Scripting 12 | Package registry (OSV) |
| suse:nodejs6 | 6.17.0-11.24.1 · SUSE:OpenStack Cloud 7 | Package registry (OSV) |
| suse:nodejs8 | 8.15.1-3.14.1 · SUSE:Linux Enterprise Module for Web and Scripting 15 | Package registry (OSV) |
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.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:0 | 2019-02-24 |
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.
- First PoC-33 d
- Published
- TodayOct 28, 2026+2771 d
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.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- lists.opensuse.org/opensuse-security-announce/2019-04/msg00046.html
- lists.opensuse.org/opensuse-security-announce/2019-04/msg00059.html
- access.redhat.com/errata/RHSA-2019:1821
- nodejs.org/en/blog/vulnerability/february-2019-security-releases/
- security.gentoo.org/glsa/202003-48
- security.netapp.com/advisory/ntap-20190502-0008/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.