CVE-2019-5739
published 2019-03-28CVE-2019-5739: 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…
PriorityP339high7.5CVSS 3.1
AVNACLPRNUINSUCNINAH
EPSS
5.05%
91.3th percentile
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.
Affected
8 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | nodejs | < nodejs 8.9.3~dfsg-5 (bookworm) | nodejs 8.9.3~dfsg-5 (bookworm) |
| node.js | node.js | — | — |
| nodejs | node.js | <= 6.16.0 | — |
| nodejs | nodejs | >= 0 < 8.9.3~dfsg-5 | 8.9.3~dfsg-5 |
| nodejs | nodejs | >= 0 < 8.9.3~dfsg-5 | 8.9.3~dfsg-5 |
| nodejs | nodejs | >= 0 < 8.9.3~dfsg-5 | 8.9.3~dfsg-5 |
| nodejs | nodejs | >= 0 < 8.9.3~dfsg-5 | 8.9.3~dfsg-5 |
| opensuse | leap | — | — |
CVSS provenance
nvdv3.17.5HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:N/I:N/A:P
osv7.5HIGH
vendor_debian7.5LOW
vendor_redhat7.5HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-wr35-fh22-q84x: Keep-alive HTTP and HTTPS connections can remain open and inactive for up to 2 minutes in Node
ghsa_unreviewed·2022-05-13
CVE-2019-5739 [HIGH] CWE-770 GHSA-wr35-fh22-q84x: Keep-alive HTTP and HTTPS connections can remain open and inactive for up to 2 minutes in Node
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.
OSV
CVE-2019-5739: Keep-alive HTTP and HTTPS connections can remain open and inactive for up to 2 minutes in Node
osv·2019-03-28·CVSS 7.5
CVE-2019-5739 [HIGH] CVE-2019-5739: Keep-alive HTTP and HTTPS connections can remain open and inactive for up to 2 minutes in Node
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.
Red Hat
nodejs: DoS with keep-alive HTTP connection
vendor_redhat·2019-02-28·CVSS 7.5
CVE-2019-5739 [HIGH] CWE-400 nodejs: DoS with keep-alive HTTP connection
nodejs: DoS with keep-alive HTTP connection
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.
Package: nodejs:10/nodejs (Red Hat Enterprise Linux 8) - Not affected
Package: nodejs (Red Hat OpenShift Container Platform 3.10) - Fix deferred
Package: nodejs (Red Hat OpenShift Container Platform 3.6) - Out of support scope
Package: nodejs (Red Hat OpenShift Container Platform 3.7) - Out of support scope
Package: nodejs (Red Hat OpenShift Container Platform 3.9) -
Debian
CVE-2019-5739: nodejs - Keep-alive HTTP and HTTPS connections can remain open and inactive for up to 2 m...
vendor_debian·2019·CVSS 7.5
CVE-2019-5739 [HIGH] CVE-2019-5739: nodejs - Keep-alive HTTP and HTTPS connections can remain open and inactive for up to 2 m...
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.
Scope: local
bookworm: resolved (fixed in 8.9.3~dfsg-5)
bullseye: resolved (fixed in 8.9.3~dfsg-5)
forky: resolved (fixed in 8.9.3~dfsg-5)
sid: resolved (fixed in 8.9.3~dfsg-5)
trixie: resolved (fixed in 8.9.3~dfsg-5)
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2019-5739 nodejs: DoS with keep-alive HTTP connection
bugzilla·2019-03-20·CVSS 7.5
CVE-2019-5739 [HIGH] CVE-2019-5739 nodejs: DoS with keep-alive HTTP connection
CVE-2019-5739 nodejs: DoS with keep-alive HTTP connection
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/
Discussion:
Created nodejs tracking bugs for this issue:
Affects: epel-7 [bug 1690817]
---
Created nodejs tracking bugs for this issue:
Affects: fedora-28 [bug 1690818]
---
According to the External Reference (https://node
Bugzilla
CVE-2019-5739 nodejs: DoS with keep-alive HTTP connection [epel-7]
bugzilla·2019-03-20·CVSS 7.5
CVE-2019-5739 [HIGH] CVE-2019-5739 nodejs: DoS with keep-alive HTTP connection [epel-7]
CVE-2019-5739 nodejs: DoS with keep-alive HTTP connection [epel-7]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-7.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
Discussion:
Use the following template to for the 'fedpkg update'
http://lists.opensuse.org/opensuse-security-announce/2019-03/msg00041.htmlhttp://lists.opensuse.org/opensuse-security-announce/2019-04/msg00046.htmlhttps://nodejs.org/en/blog/vulnerability/february-2019-security-releases/https://security.gentoo.org/glsa/202003-48https://security.netapp.com/advisory/ntap-20190502-0008/http://lists.opensuse.org/opensuse-security-announce/2019-03/msg00041.htmlhttp://lists.opensuse.org/opensuse-security-announce/2019-04/msg00046.htmlhttps://nodejs.org/en/blog/vulnerability/february-2019-security-releases/https://security.gentoo.org/glsa/202003-48https://security.netapp.com/advisory/ntap-20190502-0008/
2019-03-28
Published