Bug 1690798 (CVE-2019-5739) - CVE-2019-5739 nodejs: DoS with keep-alive HTTP connection
Summary: CVE-2019-5739 nodejs: DoS with keep-alive HTTP connection
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2019-5739
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1690817 1690818 1721039 1721040 1721041 1721042
Blocks: 1690811
TreeView+ depends on / blocked
 
Reported: 2019-03-20 09:35 UTC by Dhananjay Arunesh
Modified: 2021-10-27 03:26 UTC (History)
16 users (show)

Fixed In Version: nodejs 6.17.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-27 03:26:14 UTC
Embargoed:

Attachments (Terms of Use)

Description Dhananjay Arunesh 2019-03-20 09:35:48 UTC 
A vuneability was found in Node.js in which keep-alive HTTP and HTTPS connections can remain open and inactive for up to 2 minutes in Node.js 6.16.0 and earlier. Node.js 8.0.0 introduced a dedicated server.keepAliveTimeout which defaults to 5 seconds. The behavior in Node.js 6.16.0 and earlier is a potential Denial of Service (DoS) attack vector. Node.js 6.17.0 introduces server.keepAliveTimeout and the 5-second default.

Reference:
https://nodejs.org/en/blog/vulnerability/february-2019-security-releases/
Comment 1 Dhananjay Arunesh 2019-03-20 09:56:57 UTC 
Created nodejs tracking bugs for this issue:

Affects: epel-7 [bug 1690817]
Comment 2 Dhananjay Arunesh 2019-03-20 09:57:31 UTC 
Created nodejs tracking bugs for this issue:

Affects: fedora-28 [bug 1690818]
Comment 5 Riccardo Schirone 2019-05-17 13:40:04 UTC 
According to the External Reference (https://nodejs.org/en/blog/vulnerability/february-2019-security-releases/) nodejs 8 and nodejs 10 are not vulnerable to this flaw.
Comment 6 Riccardo Schirone 2019-05-17 13:40:07 UTC 
External References:

https://nodejs.org/en/blog/vulnerability/february-2019-security-releases/
Note You need to log in before you can comment on or make changes to this bug.