Skip to content

chore(deps): update node.js to v16 #1542

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 13, 2022
Merged

chore(deps): update node.js to v16 #1542

merged 1 commit into from
Jan 13, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 26, 2021

WhiteSource Renovate

This PR contains the following updates:

Package Type Update Change
node engines major >=10.9.0 <15.0.0 -> >=10.9.0 <17.0.0
@types/node devDependencies major 14.17.32 -> 16.11.19

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: 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, click this checkbox.

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

@google-cla google-cla bot added the cla: yes label Oct 26, 2021
@atscott atscott added the blocked A PR that is blocked by some dependency and should not be merged. label Nov 2, 2021
@atscott
Copy link
Collaborator

atscott commented Nov 2, 2021

Blocked on testing this to ensure everything works correctly, especially with respect to loading the v12 language service for view engine.

@renovate renovate bot force-pushed the renovate/node-16.x branch 4 times, most recently from 13c6bc0 to 13da0e5 Compare November 2, 2021 17:20
@atscott atscott removed the blocked A PR that is blocked by some dependency and should not be merged. label Nov 2, 2021
@atscott
Copy link
Collaborator

atscott commented Nov 2, 2021

This should be fine because the min version was not changed. As long as CI still passes, this is good to go. CI currently is set up to install node 14. As long as we support VE, the min version must always be at most v14 and CI cannot install anything greater than 14 in order to be able to install @angular/language-service v12: https://github.com/angular/angular/blob/8d060dd2f229efb130c8428c7fbaa8a37280acef/package.json#L11

If CI can install another version of node when navigating to the v12_language_service folder and doing yarn install, then we could change this requirement.

@atscott atscott added action: merge Ready to merge target: major This PR is targeted for the next major release labels Nov 2, 2021
@renovate renovate bot force-pushed the renovate/node-16.x branch 2 times, most recently from ed5b25f to 349b0dc Compare November 8, 2021 23:46
@renovate renovate bot force-pushed the renovate/node-16.x branch 3 times, most recently from 5cb2928 to 66bc1a3 Compare November 23, 2021 20:26
@renovate renovate bot force-pushed the renovate/node-16.x branch from 66bc1a3 to b7ddbbe Compare November 30, 2021 01:30
@renovate renovate bot force-pushed the renovate/node-16.x branch from b7ddbbe to 4e3e3be Compare December 7, 2021 10:08
@renovate renovate bot force-pushed the renovate/node-16.x branch 3 times, most recently from a0c4586 to 640e4a7 Compare December 20, 2021 23:58
@renovate renovate bot force-pushed the renovate/node-16.x branch 2 times, most recently from f1733ed to 4d31ffb Compare December 23, 2021 11:02
@renovate renovate bot force-pushed the renovate/node-16.x branch 2 times, most recently from f297835 to 0ce613f Compare January 4, 2022 19:45
@atscott atscott added target: patch This PR is targeted for the next patch release and removed target: major This PR is targeted for the next major release labels Jan 13, 2022
@renovate renovate bot force-pushed the renovate/node-16.x branch from 0ce613f to 5392575 Compare January 13, 2022 21:14
@atscott atscott removed the target: patch This PR is targeted for the next patch release label Jan 13, 2022
@atscott atscott added the target: minor This PR is targeted for the next minor release label Jan 13, 2022
@atscott atscott merged commit 9cb8461 into master Jan 13, 2022
@atscott atscott deleted the renovate/node-16.x branch January 13, 2022 21:22
atscott added a commit to atscott/vscode-ng-language-service that referenced this pull request Jan 19, 2022
atscott added a commit that referenced this pull request Jan 19, 2022
* Revert "chore(deps): update dependency @types/node to v16.11.20 (#1596)"

This reverts commit a5f0986.

* Revert "chore(deps): update node.js to v16 (#1542)"

This reverts commit 9cb8461.
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Feb 13, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge Ready to merge cla: yes target: minor This PR is targeted for the next minor release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants