Skip to content
This repository has been archived by the owner on Jun 7, 2022. It is now read-only.

Update Node.js to v16 #439

Closed
wants to merge 1 commit into from
Closed

Update Node.js to v16 #439

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 7, 2021

WhiteSource Renovate

This PR contains the following updates:

Package Type Update New value References Sourcegraph
node engines major >=v16.13.2 source code search for "node"
@types/node devDependencies major 16.11.21 source code search for "@types/node"

Release Notes

nodejs/node

v16.13.2

Compare Source

This is a security release.

Notable changes
Improper handling of URI Subject Alternative Names (Medium)(CVE-2021-44531)

Accepting arbitrary Subject Alternative Name (SAN) types, unless a PKI is specifically defined to use a particular SAN type, can result in bypassing name-constrained intermediates. Node.js was accepting URI SAN types, which PKIs are often not defined to use. Additionally, when a protocol allows URI SANs, Node.js did not match the URI correctly.

Versions of Node.js with the fix for this disable the URI SAN type when checking a certificate against a hostname. This behavior can be reverted through the --security-revert command-line option.

More details will be available at CVE-2021-44531 after publication.

Certificate Verification Bypass via String Injection (Medium)(CVE-2021-44532)

Node.js converts SANs (Subject Alternative Names) to a string format. It uses this string to check peer certificates against hostnames when validating connections. The string format was subject to an injection vulnerability when name constraints were used within a certificate chain, allowing the bypass of these name constraints.

Versions of Node.js with the fix for this escape SANs containing the problematic characters in order to prevent the injection. This behavior can be reverted through the --security-revert command-line option.

More details will be available at CVE-2021-44532 after publication.

Incorrect handling of certificate subject and issuer fields (Medium)(CVE-2021-44533)

Node.js did not handle multi-value Relative Distinguished Names correctly. Attackers could craft certificate subjects containing a single-value Relative Distinguished Name that would be interpreted as a multi-value Relative Distinguished Name, for example, in order to inject a Common Name that would allow bypassing the certificate subject verification.

Affected versions of Node.js do not accept multi-value Relative Distinguished Names and are thus not vulnerable to such attacks themselves. However, third-party code that uses node's ambiguous presentation of certificate subjects may be vulnerable.

More details will be available at CVE-2021-44533 after publication.

Prototype pollution via console.table properties (Low)(CVE-2022-21824)

Due to the formatting logic of the console.table() function it was not safe to allow user controlled input to be passed to the properties parameter while simultaneously passing a plain object with at least one property as the first parameter, which could be __proto__. The prototype pollution has very limited control, in that it only allows an empty string to be assigned numerical keys of the object prototype.

Versions of Node.js with the fix for this use a null protoype for the object these properties are being assigned to.

More details will be available at CVE-2022-21824 after publication.

Thanks to Patrik Oldsberg (rugvip) for reporting this vulnerability.

Commits

v16.13.1

Compare Source

Notable Changes
  • [c14eb2325d] - deps: upgrade npm to 8.1.2 (npm team) #​40643
  • [a901b6c53c] - deps: update c-ares to 1.18.1 (Richard Lau) #​40660
    • This release contains a c-ares update to fix a regression introduced in Node.js v16.6.2 resolving CNAME records containing underscores (#​39780).
  • [755c08573f] - doc: add VoltrexMaster to collaborators (voltrexmaster) #​40566
  • [881dd7ba2a] - lib: fix regular expression to detect `/` and `\` (Francesco Trotta) #​40325
Commits

v16.13.0

Compare Source

Notable Changes

This release marks the transition of Node.js 16.x into Long Term Support (LTS)
with the codename 'Gallium'. The 16.x release line now moves into "Active LTS"
and will remain so until October 2022. After that time, it will move into
"Maintenance" until end of life in April 2024.

v16.12.0

Compare Source

Notable Changes
Experimental ESM Loader Hooks API

Node.js ESM Loader hooks have been consolidated to represent the steps involved needed to facilitate future loader chaining:

  1. resolve: resolve [+ getFormat]
  2. load: getFormat + getSource + transformSource

For consistency, getGlobalPreloadCode has been renamed to globalPreload.

A loader exporting obsolete hook(s) will trigger a single deprecation warning (per loader) listing the errant hooks.

Contributed by Jacob Smith, Geoffrey Booth, and Bradley Farias - https://github.com/nodejs/node/pull/37468

Other Notable Changes
Commits

v16.11.1

Compare Source

This is a security release.

Notable changes
  • CVE-2021-22959: HTTP Request Smuggling due to spaced in headers (Medium)
    • The http parser accepts requests with a space (SP) right after the header name before the colon. This can lead to HTTP Request Smuggling (HRS). More details will be available at CVE-2021-22959 after publication.
  • CVE-2021-22960: HTTP Request Smuggling when parsing the body (Medium)
    • The parse ignores chunk extensions when parsing the body of chunked requests. This leads to HTTP Request Smuggling (HRS) under certain conditions. More details will be available at CVE-2021-22960 after publication.
Commits

v16.11.0

Compare Source

Notable Changes
  • crypto
    • update root certificates (Richard Lau) #​40280
  • deps
    • upgrade npm to 8.0.0 (npm team) #​40369
    • update nghttp2 to v1.45.1 (thunder-coding) #​40206
    • update V8 to 9.4.146.19 (Michaël Zasso) #​40285
  • tools
    • update certdata.txt (Richard Lau) #​40280
Commits

Configuration

📅 Schedule: "on the 1st through 7th day of the month" in timezone America/Los_Angeles.

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@renovate renovate bot requested a review from a team as a code owner May 7, 2021 13:25
@renovate renovate bot added the bot label May 7, 2021
@renovate renovate bot force-pushed the renovate/node-16.x branch 4 times, most recently from 167b265 to 2ff1ae5 Compare May 20, 2021 00:11
@renovate renovate bot force-pushed the renovate/node-16.x branch 3 times, most recently from 40798c2 to 8265eb1 Compare May 28, 2021 05:34
@renovate renovate bot force-pushed the renovate/node-16.x branch 4 times, most recently from 59984d9 to 7bc72d3 Compare June 4, 2021 03:56
@renovate renovate bot force-pushed the renovate/node-16.x branch 3 times, most recently from e7fb704 to b06a0d2 Compare June 16, 2021 11:22
@renovate renovate bot force-pushed the renovate/node-16.x branch 3 times, most recently from 8e31ea1 to 8b41aed Compare June 27, 2021 06:42
@renovate renovate bot force-pushed the renovate/node-16.x branch 10 times, most recently from 5ce3f16 to d9e253e Compare July 7, 2021 23:54
@renovate renovate bot closed this Oct 20, 2021
@renovate renovate bot deleted the renovate/node-16.x branch October 20, 2021 20:01
@renovate renovate bot changed the title Update Node.js to v16 - autoclosed Update Node.js to v16 Oct 26, 2021
@renovate renovate bot restored the renovate/node-16.x branch October 26, 2021 00:09
@renovate renovate bot reopened this Oct 26, 2021
@renovate renovate bot force-pushed the renovate/node-16.x branch 3 times, most recently from 2c7d9d5 to 3444897 Compare November 1, 2021 14:51
@renovate renovate bot force-pushed the renovate/node-16.x branch 3 times, most recently from 7109176 to 64c763d Compare November 23, 2021 20:52
@renovate renovate bot force-pushed the renovate/node-16.x branch 3 times, most recently from 5d5c823 to ca79753 Compare December 1, 2021 19:06
@renovate renovate bot force-pushed the renovate/node-16.x branch 3 times, most recently from 9836468 to cef432f Compare December 21, 2021 00:16
@renovate renovate bot force-pushed the renovate/node-16.x branch 2 times, most recently from de234a2 to c210799 Compare December 23, 2021 11:05
@renovate renovate bot force-pushed the renovate/node-16.x branch 2 times, most recently from 5ba6f90 to c5f8d47 Compare January 4, 2022 21:23
@renovate renovate bot force-pushed the renovate/node-16.x branch 2 times, most recently from ba0a2a2 to 4a62738 Compare January 17, 2022 09:23
@renovate
Copy link
Contributor Author

renovate bot commented Jan 26, 2022

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 16.x releases. However, if you upgrade to 16.x manually then Renovate will reenable minor and patch updates automatically.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.

@renovate renovate bot deleted the renovate/node-16.x branch January 26, 2022 08:48
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants