CVE-2019-5737
published 2019-03-28CVE-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 Service (DoS) by…
PriorityP347high7.5CVSS 3.1
AVNACLPRNUINSUCNINAH
EPSS
16.18%
96.6th percentile
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.
Affected
14 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | nodejs | < nodejs 10.15.2~dfsg-1 (bookworm) | nodejs 10.15.2~dfsg-1 (bookworm) |
| msrc | cm1_nodejs_14.17.2-1_on_cbl_mariner_1.0 | — | — |
| nodejs | node.js | >= 10.0.0 < 10.15.2 | 10.15.2 |
| nodejs | node.js | >= 11.0.0 < 11.10.1 | 11.10.1 |
| nodejs | node.js | >= 6.0.0 < 6.17.0 | 6.17.0 |
| nodejs | node.js | >= 8.0.0 < 8.15.1 | 8.15.1 |
| nodejs | nodejs | >= 0 < 10.15.2~dfsg-1 | 10.15.2~dfsg-1 |
| nodejs | nodejs | >= 0 < 10.15.2~dfsg-1 | 10.15.2~dfsg-1 |
| nodejs | nodejs | >= 0 < 10.15.2~dfsg-1 | 10.15.2~dfsg-1 |
| nodejs | nodejs | >= 0 < 10.15.2~dfsg-1 | 10.15.2~dfsg-1 |
| nodejs | nodejs | >= 0 < 0.10.25~dfsg2-2ubuntu1.2+esm1 | 0.10.25~dfsg2-2ubuntu1.2+esm1 |
| nodejs | nodejs | >= 0 < 4.2.6~dfsg-1ubuntu4.2+esm1 | 4.2.6~dfsg-1ubuntu4.2+esm1 |
| nodejs | nodejs | >= 0 < 8.10.0~dfsg-2ubuntu0.4+esm1 | 8.10.0~dfsg-2ubuntu0.4+esm1 |
| 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_msrc7.5HIGH
vendor_redhat7.5HIGH
vendor_ubuntu5.9MEDIUM
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.
Ubuntu
Node.js vulnerabilities
vendor_ubuntu·2021-03-15·CVSS 5.9
CVE-2018-7160 [MEDIUM] Node.js vulnerabilities
Title: Node.js vulnerabilities
Summary: Several security issues were fixed in Node.js.
Alexander Minozhenko and James Bunton discovered that Node.js did not
properly handle wildcards in name fields of X.509 TLS certificates. An
attacker could use this vulnerability to execute a machine-in-the-middle-
attack. This issue only affected Ubuntu 14.04 ESM and 16.04 ESM. (CVE-2016-7099)
It was discovered that Node.js incorrectly handled certain NAPTR responses.
A remote attacker could possibly use this issue to cause applications using
Node.js to crash, resulting in a denial of service. This issue only affected
Ubuntu 16.04 ESM. (CVE-2017-1000381)
Nikita Skovoroda discovered that Node.js mishandled certain input, leading
to an out of bounds write. An attacker could use this vulnerability to
c
Microsoft
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
vendor_msrc·2019-03-12·CVSS 7.5
CVE-2019-5737 [HIGH] CWE-770 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
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.
FAQ: Is Azure Linux the only Microsoft product that includes this open-source library and is therefore potentially affected by this vulnerability?
One of the main benefits
Red Hat
nodejs: Insufficient Slowloris fix causing DoS via server.headersTimeout bypass
vendor_redhat·2019-02-28·CVSS 7.5
CVE-2019-5737 [HIGH] CWE-400 nodejs: Insufficient Slowloris fix causing DoS via server.headersTimeout bypass
nodejs: Insufficient Slowloris fix causing DoS via server.headersTimeout bypass
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.
It was found that the original fix for Slowloris, CVE-2018-12122, was insufficient.
Debian
CVE-2019-5737: nodejs - In Node.js including 6.x before 6.17.0, 8.x before 8.15.1, 10.x before 10.15.2, ...
vendor_debian·2019·CVSS 7.5
CVE-2019-5737 [HIGH] CVE-2019-5737: nodejs - In Node.js including 6.x before 6.17.0, 8.x before 8.15.1, 10.x before 10.15.2, ...
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.
Scope: local
bookworm: resolved (fixed in 10.15.2~dfsg-1)
bullseye: resolved (fixed in 10.15.2~dfsg-1)
forky: resolved (fixed in 10.15.2~dfsg-1)
sid: resolved (fixed
GHSA
GHSA-24mv-c2pp-2q4f: In Node
ghsa_unreviewed·2022-05-13·CVSS 7.5
CVE-2019-5737 [HIGH] CWE-400 GHSA-24mv-c2pp-2q4f: In Node
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.
OSV
nodejs vulnerabilities
osv·2021-03-15·CVSS 5.9
CVE-2016-7099 [MEDIUM] nodejs vulnerabilities
nodejs vulnerabilities
Alexander Minozhenko and James Bunton discovered that Node.js did not
properly handle wildcards in name fields of X.509 TLS certificates. An
attacker could use this vulnerability to execute a machine-in-the-middle-
attack. This issue only affected Ubuntu 14.04 ESM and 16.04 ESM. (CVE-2016-7099)
It was discovered that Node.js incorrectly handled certain NAPTR responses.
A remote attacker could possibly use this issue to cause applications using
Node.js to crash, resulting in a denial of service. This issue only affected
Ubuntu 16.04 ESM. (CVE-2017-1000381)
Nikita Skovoroda discovered that Node.js mishandled certain input, leading
to an out of bounds write. An attacker could use this vulnerability to
cause a denial of service (crash) or possibly execute arbitrary co
OSV
CVE-2019-5737: In Node
osv·2019-03-28·CVSS 7.5
CVE-2019-5737 [HIGH] CVE-2019-5737: In Node
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.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2019-5737 nodejs: Insufficient Slowloris fix causing DoS via server.headersTimeout bypass
bugzilla·2019-03-20·CVSS 7.5
CVE-2019-5737 [HIGH] CVE-2019-5737 nodejs: Insufficient Slowloris fix causing DoS via server.headersTimeout bypass
CVE-2019-5737 nodejs: Insufficient Slowloris fix causing DoS via server.headersTimeout bypass
All actively supported release lines are vulnerable and the severity is LOW. 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 thereby keeping the connection and associated resources alive for a long period of time. Attack potential is mitigated by the use of a load balancer or other proxy layer.
Reference:
https://nodejs.org/en/blog/vulnerability/february-2019-security-releases/
Discussion:
Created nodejs tracking bugs for this issue:
Affects: fedora-all [bug 1690814]
---
Created nodejs tracking bugs for this issue:
Affects: epel-7 [bug 1690815]
---
Upstream Commit: https://github.com/nodejs/
Bugzilla
CVE-2019-5737 nodejs: insufficient Slowloris fix causing DoS via server.headersTimeout bypass [fedora-all]
bugzilla·2019-03-20·CVSS 7.5
CVE-2019-5737 [HIGH] CVE-2019-5737 nodejs: insufficient Slowloris fix causing DoS via server.headersTimeout bypass [fedora-all]
CVE-2019-5737 nodejs: insufficient Slowloris fix causing DoS via server.headersTimeout bypass [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
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.
NOTE: this issue affect
Bugzilla
CVE-2019-5737 nodejs: insufficient Slowloris fix causing DoS via server.headersTimeout bypass [epel-7]
bugzilla·2019-03-20·CVSS 7.5
CVE-2019-5737 [HIGH] CVE-2019-5737 nodejs: insufficient Slowloris fix causing DoS via server.headersTimeout bypass [epel-7]
CVE-2019-5737 nodejs: insufficient Slowloris fix causing DoS via server.headersTimeout bypass [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
http://lists.opensuse.org/opensuse-security-announce/2019-03/msg00041.htmlhttp://lists.opensuse.org/opensuse-security-announce/2019-04/msg00046.htmlhttp://lists.opensuse.org/opensuse-security-announce/2019-04/msg00059.htmlhttps://access.redhat.com/errata/RHSA-2019:1821https://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.htmlhttp://lists.opensuse.org/opensuse-security-announce/2019-04/msg00059.htmlhttps://access.redhat.com/errata/RHSA-2019:1821https://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