Opened 6 years ago
Closed 6 years ago
#14462 closed enhancement (fixed)
node.js-14.15.4
| Reported by: | Bruce Dubbs | Owned by: | Douglas R. Reno |
|---|---|---|---|
| Priority: | high | Milestone: | 10.1 |
| Component: | BOOK | Version: | SVN |
| Severity: | medium | Keywords: | |
| Cc: |
Description
New point version.
Change History (4)
comment:1 by , 6 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 6 years ago
| Priority: | normal → high |
|---|
comment:3 by , 6 years ago
2021-01-04, Version 14.15.4 'Fermium' (LTS), @BethGriggs
This is a security release.
Notable Changes
Vulnerabilities fixed:
CVE-2020-1971: OpenSSL - EDIPARTYNAME NULL pointer de-reference (High)
This is a vulnerability in OpenSSL which may be exploited through Node.js. You can read more about it in https://www.openssl.org/news/secadv/20201208.txt
CVE-2020-8265: use-after-free in TLSWrap (High)
Affected Node.js versions are vulnerable to a use-after-free bug in its TLS implementation. When writing to a TLS enabled socket, node::StreamBase::Write calls node::TLSWrap::DoWrite with a freshly allocated WriteWrap object as first argument. If the DoWrite method does not return an error, this object is passed back to the caller as part of a StreamWriteResult structure. This may be exploited to corrupt memory leading to a Denial of Service or potentially other exploits.
CVE-2020-8287: HTTP Request Smuggling in nodejs (Low)
Affected versions of Node.js allow two copies of a header field in a http request. For example, two Transfer-Encoding header fields. In this case Node.js identifies the first header field and ignores the second. This can lead to HTTP Request Smuggling (https://cwe.mitre.org/data/definitions/444.html).
Commits
[305c0f4977] - deps: upgrade npm to 6.14.10 (Ruy Adorno) #36571
[d62c650f75] - deps: update archs files for OpenSSL-1.1.1i (Myles Borins) #36521
[2de2672eb5] - deps: upgrade openssl sources to 1.1.1i (Myles Borins) #36521
[7ecac8143f] - http: add test for http transfer encoding smuggling (Matteo Collina) nodejs-private/node-private#228
[641f786bb1] - http: unset F_CHUNKED on new Transfer-Encoding (Matteo Collina) nodejs-private/node-private#228
[4f8772f9b7] - src: retain pointers to WriteWrap/ShutdownWrap (James M Snell) nodejs-private/node-private#23
Note:
See TracTickets
for help on using tickets.

(Update 4-Jan-2021) Security releases available Updates are now available for v10,x, v12.x, v14.x and v15.x Node.js release lines for the following issues. In addition to the vulnerabilities listed below, these releases also include an update to npm in order to resolve an issue that was reported against npm by security scanners even though it was not vulnerable. use-after-free in TLSWrap (High) (CVE-2020-8265) Affected Node.js versions are vulnerable to a use-after-free bug in its TLS implementation. When writing to a TLS enabled socket, node::StreamBase::Write calls node::TLSWrap::DoWrite with a freshly allocated WriteWrap object as first argument. If the DoWrite method does not return an error, this object is passed back to the caller as part of a StreamWriteResult structure. This may be exploited to corrupt memory leading to a Denial of Service or potentially other exploits. Impacts: All versions of the 15.x, 14.x, 12.x and 10.x releases lines Thank you to Felix Wilhelm from Google Project Zero for reporting this vulnerability. HTTP Request Smuggling in nodejs (CVE-2020-8287) Affected versions of Node.js allow two copies of a header field in a http request. For example, two Transfer-Encoding header fields. In this case Node.js identifies the first header field and ignores the second. This can lead to HTTP Request Smuggling (https://cwe.mitre.org/data/definitions/444.html). Impacts: All versions of the 15.x, 14.x, 12.x and 10.x releases lines Thank you to niubl who works at TSRC(Tencent Security Response Center) for reporting this vulnerability OpenSSL - EDIPARTYNAME NULL pointer de-reference (CVE-2020-1971) This is a vulnerability in OpenSSL which may be exploited through Node.js. You can read more about it in https://www.openssl.org/news/secadv/20201208.txt Impacts: All versions of the 14.x, 12.x and 10.x release lines Versions of the 15.x line before 15.5.0 which included an update to the latest OpenSSL.