CVE-2019-5739
Keep-alive HTTP and HTTPS connections can remain open and inactive for up to 2 minutes in Node.js...
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.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Exploit likelihood
What each source reports
NVD Score used
7.5
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.
- Record
CVE-2019-5739- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - CVSS 2.0
- 5.0 Medium
AV:N/AC:L/Au:N/C:N/I:N/A:P - Weakness
- CWE-400, CWE-770
- Updated
- 2026-11-02
CVE List No score
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.
- Record
CVE-2019-5739- Weakness
- CWE-400
- Updated
- 2026-11-02
EUVDEUVD-2019-15312 No score
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.
- Record
EUVD-2019-15312- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-wr35-fh22-q84x
7.5
Keep-alive HTTP and HTTPS connections can remain open and inactive for up to 2 minutes in Node.js...
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.
- Record
GHSA-wr35-fh22-q84x- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-770
- Updated
- 2026-11-02
OSV
7.5
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.
- Record
CVE-2019-5739- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVDEBIAN-CVE-2019-5739
7.5
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.
- Record
DEBIAN-CVE-2019-5739- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
Show 4 moreShow less
OSVUBUNTU-CVE-2019-5739
7.5
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.
- Record
UBUNTU-CVE-2019-5739- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVMGASA-2019-0277 No score
Updated nodejs packages fix security vulnerabilities
This update provides nodejs v6.17.1 fixing at least the following security issues:
The c-ares function ares_parse_naptr_reply(), which is used for parsing NAPTR responses, could be triggered to read memory outside of the given input buffer (CVE-2017-1000381)
Fix for 'path' module regular expression denial of service (CVE-2018-7158)
Reject spaces in HTTP Content-Length header values (CVE-2018-7159)
Fix for inspector DNS rebinding vulnerability (CVE-2018-7160)
buffer: Fixes Denial of Service vulnerability where calling Buffer.fill() could hang (CVE-2018-7167)
buffer: Fix out-of-bounds (OOB) write in Buffer.write() for UCS-2 encoding (CVE-2018-12115)
Node.js: HTTP request splitting (CVE-2018-12116)
Node.js: Debugger port 5858 listens on any interface by default (CVE-2018-12120)
Node.js: Denial of Service with large HTTP headers (CVE-2018-12121)
Node.js: Slowloris HTTP Denial of Service (CVE-2018-12122)
Node.js: Hostname spoofing in URL parser for javascript protocol (CVE-2018-12123)
Node.js: Slowloris HTTP Denial of Service with keep-alive (CVE-2019-5737)
Node.js: Denial of Service with keep-alive HTTP connections (CVE-2019-5739)
For other fixes in this update, see the referenced release logs.
- Record
MGASA-2019-0277- Updated
- 2026-11-02
OSVSUSE-SU-2019:0658-1 No score
Security update for nodejs4
This update for nodejs4 fixes the following issues:
Security issues fixed:
- CVE-2019-5739: Fixed a potentially attack vector which could lead to Denial of Service when HTTP connection are kept active (bsc#1127533).
- CVE-2019-5737: Fixed a potentially attack vector which could lead to Denial of Service when HTTP connection are kept active (bsc#1127532).
- CVE-2019-1559: Fixed OpenSSL 0-byte Record Padding Oracle which under certain circumstances a TLS server can be forced to respond differently to a client and lead to the decryption of the data (bsc#1127080).
- Record
SUSE-SU-2019:0658-1- Updated
- 2026-11-02
OSVSUSE-SU-2019:0818-1 No score
Security update for nodejs6
This update for nodejs6 to version 6.17.0 fixes the following issues:
Security issues fixed:
- CVE-2019-5739: Fixed a potentially attack vector which could lead to Denial of Service when HTTP connection are kept active (bsc#1127533).
- CVE-2019-5737: Fixed a potentially attack vector which could lead to Denial of Service when HTTP connection are kept active (bsc#1127532).
- CVE-2019-1559: Fixed OpenSSL 0-byte Record Padding Oracle which under certain circumstances a TLS server can be forced to respond differently to a client and lead to the decryption of the data (bsc#1127080).
Release Notes: https://nodejs.org/en/blog/release/v6.17.0/
- Record
SUSE-SU-2019:0818-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
nodejsDebian:12 |
before 8.9.3~dfsg-5 | 8.9.3~dfsg-5 |
nodejsDebian:13 |
before 8.9.3~dfsg-5 | 8.9.3~dfsg-5 |
nodejsDebian:14 |
before 8.9.3~dfsg-5 | 8.9.3~dfsg-5 |
nodejsMageia:6 From an advisory covering 13 CVEs |
before 6.17.1-8.mga6 | 6.17.1-8.mga6 |
http-parserMageia:6 From an advisory covering 13 CVEs |
before 2.9.2-1.mga6 | 2.9.2-1.mga6 |
libuvMageia:6 From an advisory covering 13 CVEs |
before 1.16.1-1.mga6 | 1.16.1-1.mga6 |
nodejs4SUSE:Linux Enterprise Module for Web and Scripting 12 From an advisory covering 3 CVEs |
before 4.9.1-15.20.1 | 4.9.1-15.20.1 |
nodejs4SUSE:Enterprise Storage 4 From an advisory covering 3 CVEs |
before 4.9.1-15.20.1 | 4.9.1-15.20.1 |
nodejs6SUSE:OpenStack Cloud 7 From an advisory covering 3 CVEs |
before 6.17.0-11.24.1 | 6.17.0-11.24.1 |
nodejs6SUSE:OpenStack Cloud Crowbar 8 From an advisory covering 3 CVEs |
before 6.17.0-11.24.1 | 6.17.0-11.24.1 |
nodejs6SUSE:Linux Enterprise Module for Web and Scripting 12 From an advisory covering 3 CVEs |
before 6.17.0-11.24.1 | 6.17.0-11.24.1 |
nodejs6SUSE:Enterprise Storage 4 From an advisory covering 3 CVEs |
before 6.17.0-11.24.1 | 6.17.0-11.24.1 |
nodejsUbuntu:Pro:16.04:LTS |
All versions, plus listed versions 0.10.25~dfsg2-2ubuntu14.2.2~dfsg-14.2.3~dfsg-14.2.4~dfsg-1ubuntu14.2.4~dfsg-2 Show 7 moreShow less4.2.6~dfsg-1ubuntu14.2.6~dfsg-1ubuntu44.2.6~dfsg-1ubuntu4.14.2.6~dfsg-1ubuntu4.24.2.6~dfsg-1ubuntu4.2+esm14.2.6~dfsg-1ubuntu4.2+esm24.2.6~dfsg-1ubuntu4.2+esm3 |
None known |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, facts | ||
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2019-5739 is a high vulnerability (CVSS 7.5) in Node.js, published March 20, 2019. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 4.93%, the 92nd percentile. Fixed in nodejs 8.9.3~dfsg-5.
References
nodejs.org/en/blog/vulnerability/february-2019-security-releases
lists.opensuse.org/opensuse-security-announce/2019-03/msg00041.html
lists.opensuse.org/opensuse-security-announce/2019-04/msg00046.html
security.netapp.com/advisory/ntap-20190502-0008
security.gentoo.org/glsa/202003-48
nvd.nist.gov/vuln/detail/CVE-2019-5739
Show 34 moreShow less
github.com/advisories/GHSA-wr35-fh22-q84x
security-tracker.debian.org/tracker/CVE-2019-5739
advisories.mageia.org/MGASA-2019-0277.html
bugs.mageia.org/show_bug.cgi?id=21330
nodejs.org/en/blog/release/v6.11.0
nodejs.org/en/blog/release/v6.11.1
nodejs.org/en/blog/release/v6.11.2
nodejs.org/en/blog/release/v6.11.3
nodejs.org/en/blog/release/v6.11.4
nodejs.org/en/blog/release/v6.12.0
nodejs.org/en/blog/release/v6.12.1
nodejs.org/en/blog/release/v6.12.2
nodejs.org/en/blog/release/v6.12.3
nodejs.org/en/blog/release/v6.13.0
nodejs.org/en/blog/release/v6.13.1
nodejs.org/en/blog/release/v6.14.0
nodejs.org/en/blog/release/v6.14.1
nodejs.org/en/blog/release/v6.14.2
nodejs.org/en/blog/release/v6.14.3
nodejs.org/en/blog/release/v6.15.0
nodejs.org/en/blog/release/v6.15.1
nodejs.org/en/blog/release/v6.16.0
nodejs.org/en/blog/release/v6.17.0
nodejs.org/en/blog/release/v6.17.1
suse.com/support/update/announcement/2019/suse-su-20190658-1
bugzilla.suse.com/1127080
bugzilla.suse.com/1127532
bugzilla.suse.com/1127533
suse.com/security/cve/CVE-2019-1559
suse.com/security/cve/CVE-2019-5737
suse.com/security/cve/CVE-2019-5739
suse.com/support/update/announcement/2019/suse-su-20190818-1
ubuntu.com/security/CVE-2019-5739
cve.org/CVERecord?id=CVE-2019-5739