chore(deps): update node.js to v12.22.12 #314
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
Chore
ContributorsCommit-Lint commandsYou can trigger Commit-Lint actions by commenting on this PR:
|
|
🎉 This PR is included in version 2.5.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
12.22.7->12.22.12Release Notes
nodejs/node
v12.22.12Compare 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
1193290f3f] - deps: V8: cherry-pickcc9a8a3(devsnek) #42065333eda8d03] - doc: add a note about possible missing lines to readline.asyncIterator (Igor Mikhalev) #34675518a49c0c6] - doc: use openpgp.org for keyserver examples (Nick Schonning) #3922711aef2ad03] - doc: update release key for Danielle Adams (Danielle Adams) #36793a9c38f1003] - doc: add release key for Danielle Adams (Danielle Adams) #35545a35f553889] - doc: add release key for Bryan English (Bryan English) #421025f104e3218] - node-api: cctest on v8impl::Reference (legendecas) #38970e23c04f0dc] - node-api: avoid SecondPassCallback crash (Michael Dawson) #38899a7224c9559] - node-api: fix shutdown crashes (Michael Dawson) #3849281b4dc88f1] - node-api: make reference weak parameter an indirect link to references (Chengzhong Wu) #380002aa9ca1ea9] - node-api: fix crash in finalization (Michael Dawson) #37876a2f4206415] - node-api: stop ref gc during environment teardown (Gabriel Schulhof) #37616171bb66ccc] - node-api: force env shutdown deferring behavior (Gabriel Schulhof) #37303e707514c80] - src: fix finalization crash (James M Snell) #38250v12.22.11Compare Source
This is a security release.
Notable changes
Update to OpenSSL 1.1.1n, which addresses the following vulnerability:
BN_mod_sqrt()reachable when parsing certificates (High)(CVE-2022-0778)More details are available at https://www.openssl.org/news/secadv/20220315.txt
Fix for building Node.js 12.x with Visual Studio 2019 to allow us to continue to
run CI tests.
Commits
e3e5bf11ba] - build: pin Windows GitHub runner to windows-2019 (Richard Lau) #42349f41e7771bf] - build: fix detection of Visual Studio 2019 (Richard Lau) #42349c372ec207d] - deps: update archs files for OpenSSL-1.1.n (Richard Lau) #42348d574a1dccb] - deps: upgrade openssl sources to 1.1.1n (Richard Lau) #42348v12.22.10Compare Source
Notable changes
Commits
33899b435d] - deps: upgrade npm to 6.14.16 (Ruy Adorno) #41601d9237c46ca] - tools: update tzdata to 2021a4 (Albert Wang) #41443v12.22.9Compare 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-revertcommand-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-revertcommand-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.tableproperties (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 thepropertiesparameter 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
be69403528] - console: fix prototype pollution via console.table (Tobias Nießen) nodejs-private/node-private#30719873abfb2] - crypto,tls: implement safe x509 GeneralName format (Tobias Nießen and Akshay Kumar) nodejs-private/node-private#300ff9ac7d757] - doc: fix date for v12.22.8 (Richard Lau) #41213a5c7843cab] - src: add cve reverts and associated tests (Michael Dawson and Akshay Kumar) nodejs-private/node-private#300d4e5d1b9ca] - src: remove unused x509 functions (Tobias Nießen and Akshay Kumar) nodejs-private/node-private#3008c2db2c86b] - tls: fix handling of x509 subject and issuer (Tobias Nießen and Akshay Kumar) nodejs-private/node-private#300e0fe6a635e] - tls: drop support for URI alternative names (Tobias Nießen and Akshay Kumar) nodejs-private/node-private#300v12.22.8Compare 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
2d42295d2a] - build: pin macOS GitHub runner to macos-10.15 (Richard Lau) #4112441e09ec71b] - child_process: retain reference to data with advanced serialization (Anna Henningsen) #38728f0be07796e] - crypto: update root certificates (Richard Lau) #402804c9f920d34] - deps: update archs files for OpenSSL-1.1.1m (Richard Lau) #4117260d7d4171e] - deps: upgrade openssl sources to 1.1.1m (Richard Lau) #411727feff67419] - deps: add -fno-strict-aliasing flag to libuv (Daniel Bevenius) #40631534ac7c7c6] - deps: update c-ares to 1.18.1 (Richard Lau) #40660c019fa9b70] - deps: update to cjs-module-lexer@1.2.2 (Guy Bedford) #39402b13340eff4] - doc: add alternative version links to the packages page (Filip Skokan) #36915243b2fbfdb] - lib: fix regular expression to detect `/` and `\` (Francesco Trotta) #4032570e094a26b] - repl: fix error message printing (Anna Henningsen) #3820902b432a704] - src: fix crash in AfterGetAddrInfo (Anna Henningsen) #397357479447d6a] - test: deflake child-process-pipe-dataflow (Luigi Pinca) #40838833e199393] - tools: update certdata.txt (Richard Lau) #40280e4339fe286] - tools: add script to update c-ares (Richard Lau) #40660f50b9c1e8a] - worker: avoid potential deadlock on NearHeapLimit (Santiago Gimeno) #38403Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.
This PR has been generated by Mend Renovate. View repository job log here.