chore(deps): update dependency ws to v7.4.6 [security]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
ws	`7.3.1` -> `7.4.6`

GitHub Vulnerability Alerts

CVE-2021-32640

Impact

A specially crafted value of the Sec-Websocket-Protocol header can be used to significantly slow down a ws server.

Proof of concept

for (const length of [1000, 2000, 4000, 8000, 16000, 32000]) {
  const value = 'b' + ' '.repeat(length) + 'x';
  const start = process.hrtime.bigint();

  value.trim().split(/ *, */);

  const end = process.hrtime.bigint();

  console.log('length = %d, time = %f ns', length, end - start);
}

Patches

The vulnerability was fixed in ws@7.4.6 (https://github.com/websockets/ws/commit/00c425ec77993773d823f018f64a5c44e17023ff) and backported to ws@6.2.2 (https://github.com/websockets/ws/commit/78c676d2a1acefbc05292e9f7ea0a9457704bf1b) and ws@5.2.3 (https://github.com/websockets/ws/commit/76d47c1479002022a3e4357b3c9f0e23a68d4cd2).

Workarounds

In vulnerable versions of ws, the issue can be mitigated by reducing the maximum allowed length of the request headers using the --max-http-header-size=size and/or the maxHeaderSize options.

Credits

The vulnerability was responsibly disclosed along with a fix in private by Robert McLaughlin from University of California, Santa Barbara.

Release Notes

websockets/ws (ws)

### [`v7.4.6`](https://togithub.com/websockets/ws/releases/tag/7.4.6) [Compare Source](https://togithub.com/websockets/ws/compare/7.4.5...7.4.6) ### Bug fixes - Fixed a ReDoS vulnerability ([`00c425e`](https://togithub.com/websockets/ws/commit/00c425ec)). A specially crafted value of the `Sec-Websocket-Protocol` header could be used to significantly slow down a ws server. ```js for (const length of [1000, 2000, 4000, 8000, 16000, 32000]) { const value = 'b' + ' '.repeat(length) + 'x'; const start = process.hrtime.bigint(); value.trim().split(/ *, */); const end = process.hrtime.bigint(); console.log('length = %d, time = %f ns', length, end - start); } ``` The vulnerability was responsibly disclosed along with a fix in private by [Robert McLaughlin](https://togithub.com/robmcl4) from University of California, Santa Barbara. In vulnerable versions of ws, the issue can be mitigated by reducing the maximum allowed length of the request headers using the [`--max-http-header-size=size`](https://nodejs.org/api/cli.html#cli_max_http_header_size_size) and/or the [`maxHeaderSize`](https://nodejs.org/api/http.html#http_http_createserver_options_requestlistener) options. ### [`v7.4.5`](https://togithub.com/websockets/ws/releases/tag/7.4.5) [Compare Source](https://togithub.com/websockets/ws/compare/7.4.4...7.4.5) ### Bug fixes - UTF-8 validation is now done even if `utf-8-validate` is not installed ([`23ba6b2`](https://togithub.com/websockets/ws/commit/23ba6b29)). - Fixed an edge case where `websocket.close()` and `websocket.terminate()` did not close the connection ([`67e25ff`](https://togithub.com/websockets/ws/commit/67e25ff5)). ### [`v7.4.4`](https://togithub.com/websockets/ws/releases/tag/7.4.4) [Compare Source](https://togithub.com/websockets/ws/compare/7.4.3...7.4.4) ### Bug fixes - Fixed a bug that could cause the process to crash when using the permessage-deflate extension ([`9277437`](https://togithub.com/websockets/ws/commit/92774377)). ### [`v7.4.3`](https://togithub.com/websockets/ws/releases/tag/7.4.3) [Compare Source](https://togithub.com/websockets/ws/compare/7.4.2...7.4.3) ### Bug fixes - The deflate/inflate stream is now reset instead of reinitialized when context takeover is disabled ([#1840](https://togithub.com/websockets/ws/issues/1840)). ### [`v7.4.2`](https://togithub.com/websockets/ws/releases/tag/7.4.2) [Compare Source](https://togithub.com/websockets/ws/compare/7.4.1...7.4.2) ### Bug fixes - Silenced a deprecation warning ([`a2c0d44`](https://togithub.com/websockets/ws/commit/a2c0d447)). ### [`v7.4.1`](https://togithub.com/websockets/ws/releases/tag/7.4.1) [Compare Source](https://togithub.com/websockets/ws/compare/7.4.0...7.4.1) ### Bug fixes - Added a workaround for a double `'error'` event bug in Node.js < 13 which caused an uncaught error during the WebSocket handshake ([`38d6ab3`](https://togithub.com/websockets/ws/commit/38d6ab3b)). ### [`v7.4.0`](https://togithub.com/websockets/ws/releases/tag/7.4.0) [Compare Source](https://togithub.com/websockets/ws/compare/7.3.1...7.4.0) ### Features - The callback of `WebSocketServer.prototype.handleUpgrade()` now takes the client HTTP GET request as second argument ([`7d39f19`](https://togithub.com/websockets/ws/commit/7d39f19e)). ### Bug fixes - Read-only properties are now read-only ([`eabed8f`](https://togithub.com/websockets/ws/commit/eabed8fc)). - The `CONNECTING`, `OPEN`, `CLOSING`, `CLOSED`, `binaryType`, `bufferedAmount`, `extensions`, `onclose`, `onerror`, `onmessage`, `onopen`, `protocol`, `readyState`, and `url` properties are now enumerable ([`2069e68`](https://togithub.com/websockets/ws/commit/2069e684)).

Configuration

📅 Schedule: Branch creation - "" (UTC), 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 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.

TylorS / typed-prelude