Skip to content
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

Update all #1124

Merged
merged 1 commit into from
Jan 12, 2022
Merged

Update all #1124

merged 1 commit into from
Jan 12, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 10, 2022

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/node 16.11.18 -> 16.11.19 age adoption passing confidence
lint-staged 12.1.5 -> 12.1.7 age adoption passing confidence
mini-css-extract-plugin 2.4.5 -> 2.4.6 age adoption passing confidence
node 16.13.1 -> 16.13.2 age adoption passing confidence
rollup (source) 2.62.0 -> 2.63.0 age adoption passing confidence
shx 0.3.3 -> 0.3.4 age adoption passing confidence
webpack 5.65.0 -> 5.66.0 age adoption passing confidence

Release Notes

okonet/lint-staged

v12.1.7

Compare Source

Bug Fixes

v12.1.6

Compare Source

Bug Fixes
  • always run non-git tasks in the current working directory (893f3d7)
webpack-contrib/mini-css-extract-plugin

v2.4.6

Compare Source

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
rollup/rollup

v2.63.0

Compare Source

2022-01-04

Features
  • Report a helpful error if rollup exits due to an empty event loop when using this.load (#​4320)
  • Allow directly mutating ModuleInfo.meta for modules and never replace this object (#​4328)
  • Detect additional side effect free array prototype methods (#​4332)
Bug Fixes
  • Do not watch if CLI watch options are specified but --watch is missing (#​4335)
Pull Requests
shelljs/shx

v0.3.4

Compare Source

webpack/webpack

v5.66.0

Compare Source

Features

Bugfixes

  • fix CORS headers for experiments.lazyCompilation
  • fix [absolute-resource-path] for SourceMap module naming
  • avoid stack overflow when accessing many memory cached cache values in series

Performance

  • reduce default watchOptions.aggregateTimeout to 20ms

Configuration

📅 Schedule: "before 3am on Monday" (UTC).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

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

@renovate renovate bot force-pushed the renovate/all branch 2 times, most recently from 8569ae7 to 2622979 Compare January 11, 2022 00:18
@samouri samouri merged commit 808c786 into main Jan 12, 2022
@samouri samouri deleted the renovate/all branch January 12, 2022 14:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant