Skip to content
This repository was archived by the owner on Jul 20, 2022. It is now read-only.

chore(deps): update node.js to v18 #230

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 1, 2022

Mend Renovate

This PR contains the following updates:

Package Type Update New value References Sourcegraph
node final major 18.3.0-alpine3.14 source code search for "node"

Test plan: CI should pass with updated dependencies. No review required: this is an automated dependency update PR.


Release Notes

nodejs/node

v18.3.0

Compare Source

v18.2.0

Compare Source

v18.1.0

Compare Source

v18.0.0

Compare Source

v17.9.1

Compare Source

v17.9.0

Compare Source

v17.8.0

Compare Source

v17.7.2

Compare Source

This is a security release.

Notable Changes

Update to OpenSSL 3.0.2, which addresses the following vulnerability:

Commits

v17.7.1

Compare Source

Notable Changes
Fixed regression in url.resolve()

This release fixes an issue introduced in Node.js v17.7.0 with some URLs
that contain @. This issue affected yarn 1. This version reverts the
change that introduced the regression.

Commits

v17.6.0

Compare Source

v17.5.0

Compare Source

v17.4.0

Compare Source

v17.3.1

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

v17.3.0

Compare Source

v17.2.0

Compare Source

Notable Changes
Commits

v17.1.0

Compare Source

Notable Changes
  • [89b34ecffb] - doc: add VoltrexMaster to collaborators (voltrexmaster) #​40566
  • [95e4d29eb4] - (SEMVER-MINOR) esm: add support for JSON import assertion (Antoine du Hamel) #​40250
  • [1ddbae2d76] - (SEMVER-MINOR) lib: add unsubscribe method to non-active DC channels (simon-id) #​40433
  • [aa61551b49] - (SEMVER-MINOR) lib: add return value for DC channel.unsubscribe (simon-id) #​40433
  • [fbeb895ca6] - (SEMVER-MINOR) v8: multi-tenant promise hook api (Stephen Belanger) #​39283
Commits

v17.0.1

Compare Source

Notable Changes
Fixed distribution for native addon builds

This release fixes an issue introduced in Node.js v17.0.0, where some V8 headers
were missing from the distributed tarball, making it impossible to build native
addons. These headers are now included. #​40526

Fixed stream issues
  • Fixed a regression in stream.promises.pipeline, which was introduced in version
    16.10.0, is fixed. It is now possible again to pass an array of streams to the
    function. #​40193
  • Fixed a bug in stream.Duplex.from, which didn't work properly when an async
    generator function was passed to it. #​40499
Commits

Configuration

📅 Schedule: Branch creation - "on the 1st through 7th day of the month" in timezone America/Los_Angeles, Automerge - At any time (no schedule defined).

🚦 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 this update again.


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

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

@renovate renovate bot added the bot label May 1, 2022
@renovate renovate bot force-pushed the renovate/node-18.x branch from 56d7bfe to d6f13e3 Compare May 4, 2022 01:48
@renovate renovate bot force-pushed the renovate/node-18.x branch 3 times, most recently from c2c76a7 to eabb074 Compare May 19, 2022 05:29
@renovate renovate bot force-pushed the renovate/node-18.x branch 2 times, most recently from c89e301 to 8b3a322 Compare June 7, 2022 00:39
@renovate renovate bot force-pushed the renovate/node-18.x branch from 8b3a322 to d564586 Compare June 7, 2022 03:46
@renovate renovate bot changed the title chore(deps): update node.js to v18 chore(deps): update Node.js to v18 Jun 27, 2022
@renovate renovate bot changed the title chore(deps): update Node.js to v18 chore(deps): update node.js to v18 Jun 28, 2022
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.

1 participant