Skip to content
This repository was archived by the owner on Mar 21, 2024. It is now read-only.

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 29, 2021

Mend Renovate

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
node (source) minor 12.21.0 -> 12.22.12 age adoption passing confidence
@types/node (source) resolutions patch 12.20.6 -> 12.20.55 age adoption passing confidence
@types/node (source) devDependencies patch 12.20.6 -> 12.20.55 age adoption passing confidence

Release Notes

nodejs/node (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

v12.22.8: 2021-12-16, Version 12.22.8 'Erbium' (LTS), @​richardlau

Compare Source

Notable Changes

This release contains a c-ares update to fix a regression introduced in
Node.js 12.22.5 resolving CNAME records containing underscores
#​39780.

Root certificates have been updated to those from Mozilla's Network
Security Services 3.71 #​40281.

Commits

v12.22.7: 2021-10-12, Version 12.22.7 'Erbium' (LTS), @​danielleadams

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

v12.22.6: 2021-08-31, Version 12.22.6 'Erbium' (LTS), @​MylesBorins

Compare Source

This is a security release.

Notable Changes

These are vulnerabilities in the node-tar, arborist, and npm cli modules which
are related to the initial reports and subsequent remediation of node-tar
vulnerabilities CVE-2021-32803
and CVE-2021-32804.
Subsequent internal security review of node-tar and additional external bounty
reports have resulted in another 5 CVE being remediated in core npm CLI
dependencies including node-tar, and npm arborist.

You can read more about it in:

Commits

v12.22.5: 2021-08-11, Version 12.22.5 'Erbium' (LTS), @​BethGriggs

Compare Source

This is a security release.

Notable Changes
  • CVE-2021-3672/CVE-2021-22931: Improper handling of untypical characters in domain names (High)
    • Node.js was vulnerable to Remote Code Execution, XSS, application crashes due to missing input validation of hostnames returned by Domain Name Servers in the Node.js DNS library which can lead to the output of wrong hostnames (leading to Domain Hijacking) and injection vulnerabilities in applications using the library. You can read more about it at https://nvd.nist.gov/vuln/detail/CVE-2021-22931.
  • CVE-2021-22940: Use after free on close http2 on stream canceling (High)
  • CVE-2021-22939: Incomplete validation of rejectUnauthorized parameter (Low)
    • If the Node.js HTTPS API was used incorrectly and "undefined" was in passed for the "rejectUnauthorized" parameter, no error was returned and connections to servers with an expired certificate would have been accepted. You can read more about it at https://nvd.nist.gov/vuln/detail/CVE-2021-22939.
Commits

v12.22.4: 2021-07-29, Version 12.22.4 'Erbium' (LTS), @​richardlau

Compare Source

This is a security release.

Notable Changes
Commits

v12.22.3: 2021-07-05, Version 12.22.3 'Erbium' (LTS), @​richardlau

Compare Source

Notable Changes

Node.js 12.22.2 introduced a regression in the Windows installer on
non-English locales that is being fixed in this release. There is no
need to download this release if you are not using the Windows
installer.

Commits

v12.22.2: 2021-07-01, Version 12.22.2 'Erbium' (LTS), @​richardlau

Compare Source

This is a security release.

Notable Changes

Vulnerabilities fixed:

  • CVE-2021-22918: libuv upgrade - Out of bounds read (Medium)
    • Node.js is vulnerable to out-of-bounds read in libuv's uv__idna_toascii() function which is used to convert strings to ASCII. This is called by Node's dns module's lookup() function and can lead to information disclosures or crashes. You can read more about it in https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22918
  • CVE-2021-22921: Windows installer - Node Installer Local Privilege Escalation (Medium)
    • Node.js is vulnerable to local privilege escalation attacks under certain conditions on Windows platforms. More specifically, improper configuration of permissions in the installation directory allows an attacker to perform two different escalation attacks: PATH and DLL hijacking. You can read more about it in https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22921
  • CVE-2021-27290: npm upgrade - ssri Regular Expression Denial of Service (ReDoS) (High)
    • This is a vulnerability in the ssri npm mudule which may be vulnerable to denial of service attacks. You can read more about it in GHSA-vx3p-948g-6vhq
  • CVE-2021-23362: npm upgrade - hosted-git-info Regular Expression Denial of Service (ReDoS) (Medium)
Commits

v12.22.1: 2021-04-06, Version 12.22.1 'Erbium' (LTS), @​mylesborins

Compare Source

This is a security release.

Notable Changes

Vulnerabilities fixed:

  • CVE-2021-3450: OpenSSL - CA certificate check bypass with X509_V_FLAG_X509_STRICT (High)
  • CVE-2021-3449: OpenSSL - NULL pointer deref in signature_algorithms processing (High)
  • CVE-2020-7774: npm upgrade - Update y18n to fix Prototype-Pollution (High)
    • This is a vulnerability in the y18n npm module which may be exploited by prototype pollution. You can read more about it in GHSA-c4w7-xm78-47vh
    • Impacts:
      • All versions of the 14.x, 12.x and 10.x releases lines
Commits

v12.22.0: 2021-03-30, Version 12.22.0 'Erbium' (LTS), @​richardlau

Compare Source

Notable changes
The legacy HTTP parser is runtime deprecated

The legacy HTTP parser, selected by the --http-parser=legacy command line
option, is deprecated with the pending End-of-Life of Node.js 10.x (where it
is the only HTTP parser implementation provided) at the end of April 2021. It
will now warn on use but otherwise continue to function and may be removed in
a future Node.js 12.x release.

The default HTTP parser based on llhttp is not affected. By default it is
stricter than the now deprecated legacy HTTP parser. If interoperability with
HTTP implementations that send invalid HTTP headers is required, the HTTP
parser can be started in a less secure mode with the --insecure-http-parser
command line option.

Contributed by Beth Griggs #​37603.

ES Modules

ES Modules are now considered stable.

Contributed by Guy Bedford #​35781

node-api

Updated to node-api version 8 and added an experimental API to allow retrieval of the add-on file name.

Contributed by Gabriel Schulhof #​37652 and #​37195.

New API's to control code coverage data collection

v8.stopCoverage() and v8.takeCoverage() have been added.

Contributed by Joyee Cheung #​33807.

New API to monitor event loop utilization by Worker threads

worker.performance.eventLoopUtilization() has been added.

Contributed by Trevor Norris #​35664.

Commits

Configuration

📅 Schedule: Branch creation - "before 11am" (UTC), 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 these updates 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 added the dependencies Pull requests that update a dependency file label Mar 29, 2021
@renovate renovate bot force-pushed the renovate/node-12.x branch from bd6929e to 24fa510 Compare March 30, 2021 15:00
@renovate renovate bot changed the title Update dependency @types/node to v12.20.7 Update Node.js to v12.22.0 Mar 30, 2021
@renovate renovate bot force-pushed the renovate/node-12.x branch from 24fa510 to 8dc6db7 Compare April 6, 2021 21:04
@renovate renovate bot changed the title Update Node.js to v12.22.0 Update Node.js to v12.22.1 Apr 6, 2021
@renovate renovate bot force-pushed the renovate/node-12.x branch 3 times, most recently from 4a37a91 to fc2c99d Compare April 16, 2021 04:42
@renovate renovate bot force-pushed the renovate/node-12.x branch from fc2c99d to 3ddb428 Compare April 27, 2021 14:54
@renovate renovate bot force-pushed the renovate/node-12.x branch from 3ddb428 to f6f8625 Compare May 4, 2021 23:47
@renovate renovate bot force-pushed the renovate/node-12.x branch from f6f8625 to 89c5f90 Compare May 12, 2021 21:38
@renovate renovate bot force-pushed the renovate/node-12.x branch from 1e202e7 to a5c0383 Compare June 8, 2021 00:21
@renovate renovate bot force-pushed the renovate/node-12.x branch from a5c0383 to 3823bcc Compare July 1, 2021 16:24
@renovate renovate bot changed the title Update Node.js to v12.22.1 Update Node.js to v12.22.2 Jul 1, 2021
@renovate renovate bot force-pushed the renovate/node-12.x branch from 3823bcc to 2345b5d Compare July 5, 2021 16:02
@renovate renovate bot changed the title Update Node.js to v12.22.2 Update Node.js to v12.22.3 Jul 5, 2021
@renovate renovate bot force-pushed the renovate/node-12.x branch from 2345b5d to 9b2e787 Compare July 7, 2021 18:00
@renovate renovate bot force-pushed the renovate/node-12.x branch from 9b2e787 to 0c523e9 Compare July 24, 2021 18:03
@renovate renovate bot force-pushed the renovate/node-12.x branch from 0c523e9 to e1a02ba Compare October 18, 2021 20:22
@renovate renovate bot changed the title Update Node.js to v12.22.3 Update Node.js to v12.22.7 Oct 18, 2021
@renovate renovate bot force-pushed the renovate/node-12.x branch from e1a02ba to 8b769c9 Compare March 7, 2022 14:33
@renovate renovate bot changed the title Update Node.js to v12.22.7 Update Node.js to v12.22.10 Mar 7, 2022
@renovate renovate bot force-pushed the renovate/node-12.x branch from 8b769c9 to 27346eb Compare March 26, 2022 14:28
@renovate renovate bot changed the title Update Node.js to v12.22.10 Update Node.js to v12.22.11 Mar 26, 2022
@renovate renovate bot force-pushed the renovate/node-12.x branch from 27346eb to 8dca964 Compare April 25, 2022 02:19
@renovate renovate bot changed the title Update Node.js to v12.22.11 Update Node.js to v12.22.12 Apr 25, 2022
@renovate renovate bot force-pushed the renovate/node-12.x branch from 8dca964 to f817b59 Compare May 16, 2022 02:51
@renovate renovate bot force-pushed the renovate/node-12.x branch from f817b59 to c7f53c3 Compare June 18, 2022 22:43
@renovate renovate bot force-pushed the renovate/node-12.x branch from c7f53c3 to 3f750f0 Compare November 20, 2022 21:21
@renovate renovate bot changed the title Update Node.js to v12.22.12 Update dependency node to v12.22.12 Jul 9, 2023
@beeequeue beeequeue closed this Mar 21, 2024
@renovate
Copy link
Contributor Author

renovate bot commented Mar 21, 2024

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (12.22.12). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/node-12.x branch March 21, 2024 16:29
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants