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

chore(deps): update node.js to v12.22.12 #29

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 11, 2022

Mend Renovate

This PR contains the following updates:

Package Update Change
node patch 12.22.8 -> 12.22.12

Release Notes

nodejs/node

v12.22.12: 2022-04-05, Version 12.22.12 'Erbium' (LTS), @​richardlau

Compare Source

Notable Changes

This is planned to be the final Node.js 12 release. Node.js 12 will
reach End-of-Life status on 30 April 2022, after which it will no
receive updates. You are strongly advised to migrate your applications
to Node.js 16 or 14 (both of which are Long Term Support (LTS) releases)
to continue to receive future security updates beyond 30 April 2022.

This release fixes a shutdown crash in Node-API (formerly N-API) and a
potential stack overflow when using vm.runInNewContext().

The list of GPG keys used to sign releases and instructions on how to
fetch the keys for verifying binaries has been synchronized with the
main branch.

Commits

v12.22.11: 2022-03-17, Version 12.22.11 'Erbium' (LTS), @​richardlau

Compare Source

This is a security release.

Notable changes

Update to OpenSSL 1.1.1n, which addresses the following vulnerability:

Fix for building Node.js 12.x with Visual Studio 2019 to allow us to continue to
run CI tests.

Commits

v12.22.10: 2022-02-01, Version 12.22.10 'Erbium' (LTS), @​ruyadorno

Compare Source

Notable changes
  • Upgrade npm to 6.14.16
  • Updated ICU time zone data
Commits

v12.22.9: 2022-01-10, Version 12.22.9 'Erbium' (LTS), @​richardlau

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

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

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

Rebasing: Whenever PR is behind base branch, 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, check this box

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

@renovate renovate bot requested a review from prisis as a code owner January 11, 2022 00:53
@renovate renovate bot added Changed Changelog Changed dependency labels Jan 11, 2022
@renovate renovate bot force-pushed the renovate/node-12.x branch 3 times, most recently from 0911d37 to 396214e Compare January 18, 2022 22:09
@renovate renovate bot force-pushed the renovate/node-12.x branch from 396214e to dde0522 Compare January 24, 2022 15:53
@renovate renovate bot force-pushed the renovate/node-12.x branch 2 times, most recently from 36a9513 to 14f314c Compare February 1, 2022 20:31
@renovate renovate bot changed the title chore(deps): update node.js to v12.22.9 chore(deps): update node.js to v12.22.10 Feb 1, 2022
@renovate renovate bot force-pushed the renovate/node-12.x branch 7 times, most recently from a81e7eb to e892cea Compare February 15, 2022 15:47
@renovate renovate bot force-pushed the renovate/node-12.x branch from e892cea to 1ed70b9 Compare February 24, 2022 19:49
@renovate renovate bot force-pushed the renovate/node-12.x branch from 1ed70b9 to 3181b41 Compare March 17, 2022 23:52
@renovate renovate bot changed the title chore(deps): update node.js to v12.22.10 chore(deps): update node.js to v12.22.11 Mar 17, 2022
@renovate renovate bot changed the title chore(deps): update node.js to v12.22.11 chore(deps): update node.js to v12.22.12 Apr 5, 2022
@renovate renovate bot force-pushed the renovate/node-12.x branch from 3181b41 to 9f7f49d Compare April 5, 2022 13:38
@renovate renovate bot force-pushed the renovate/node-12.x branch from 9f7f49d to 2c5fda6 Compare April 14, 2022 12:21
@renovate renovate bot force-pushed the renovate/node-12.x branch 6 times, most recently from a5b8372 to 44a3a4b Compare May 2, 2022 00:04
@renovate renovate bot force-pushed the renovate/node-12.x branch from 44a3a4b to 22489ca Compare May 3, 2022 16:58
@renovate renovate bot force-pushed the renovate/node-12.x branch 4 times, most recently from 5196fde to 61c7472 Compare May 13, 2022 01:26
@renovate renovate bot force-pushed the renovate/node-12.x branch from 61c7472 to 2de300b Compare May 17, 2022 02:36
@renovate renovate bot force-pushed the renovate/node-12.x branch 4 times, most recently from a11cda7 to e762154 Compare June 7, 2022 23:16
@renovate renovate bot changed the title chore(deps): update node.js to v12.22.12 chore(deps): update Node.js to v12.22.12 Jun 27, 2022
@renovate renovate bot changed the title chore(deps): update Node.js to v12.22.12 chore(deps): update node.js to v12.22.12 Jun 28, 2022
@renovate renovate bot force-pushed the renovate/node-12.x branch from e762154 to 5590239 Compare June 30, 2022 01:42
@renovate renovate bot force-pushed the renovate/node-12.x branch from 5590239 to 05202ee Compare June 30, 2022 01:45
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Changed Changelog Changed dependency
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants