Node.js

News from 2021

15 Jan Node v15.6.0 (Current)
- child_process:
  - add 'overlapped' stdio flag (Thiago Padilha) #29412
  - support AbortSignal in fork (Benjamin Gruenbaum) #36603
- crypto:
  - implement basic secure heap support (James M Snell) #36779
  - fixup bug in keygen error handling (James M Snell) #36779
  - introduce X509Certificate API (James M Snell) #36804
  - implement randomuuid (James M Snell) #36729
- doc:
  - update release key for Danielle Adams (Danielle Adams) #36793
  - add dnlup to collaborators (Daniele Belardi) #36849
  - add panva to collaborators (Filip Skokan) #36802
  - add yashLadha to collaborator (Yash Ladha) #36666
- http:
  - set lifo as the default scheduling strategy in Agent (Matteo Collina) #36685
- net:
  - support abortSignal in server.listen (Nitzan Uziely) #36623
- process:
  - add direct access to rss without iterating pages (Adrien Maret) #34291
- v8:
  - fix native serdes constructors (ExE Boss) #36549
Read more...
04 Jan January 2021 Security Releases

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.
Read more...
04 Jan Node v12.20.1 (LTS)
This is a security release.
Vulnerabilities fixed:
- 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 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).
- 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
Read more...
04 Jan Node v10.23.1 (LTS)
This is a security release.
Vulnerabilities fixed:
- 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 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).
- 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
Read more...
04 Jan Node v14.15.4 (LTS)
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).
Read more...
04 Jan Node v15.5.1 (Current)
Vulnerabilities fixed:
- 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).
Read more...