Node.js 6 and 1 other: Uncontrolled Resource Consumption / Denial of Service
CVE-2019-5737 is fixed in 7 products on 2 platforms, first by Node.js 6 6.17.0, released February 28, 2019. 1 other affected product has no fix yet. It is not reported as exploited. Patch Radar priority: High.
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.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Windows apps | |||
| Node.js 6 | 6.17.0 | Node.js 6 6.17.0 | Feb 28, 2019 |
| Linux | |||
| nodejs · RHEL 8 | 1:10.16.3-2.module+el8.0.0+4214+49953fda | RHSA-2019:2925 | Sep 30, 2019 |
| nodejs · Ubuntu 18.04.6 LTS (bionic) | 8.10.0~dfsg-2ubuntu0.4+esm1 | nodejs 8.10.0~dfsg-2ubuntu0.4+esm1 | Mar 28, 2019 |
| nodejs-devel · RHEL 8 | 1:10.16.3-2.module+el8.0.0+4214+49953fda | RHSA-2019:2925 | Sep 30, 2019 |
| nodejs-docs · RHEL 8 | 1:10.16.3-2.module+el8.0.0+4214+49953fda | RHSA-2019:2925 | Sep 30, 2019 |
| nodejs-nodemon · RHEL 8 | 0:1.18.3-1.module+el8+2632+6c5111ed | RHSA-2019:2925 | Sep 30, 2019 |
| nodejs-packaging · RHEL 8 | 0:17-3.module+el8+2873+aa7dfd9a | RHSA-2019:2925 | Sep 30, 2019 |
| npm · RHEL 8 | 1:6.9.0-1.10.16.3.2.module+el8.0.0+4214+49953fda | RHSA-2019:2925 | Sep 30, 2019 |
| No fix yet | |||
| Node.js 8 (Windows apps) | No fix yet | no-fix | n/a |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.