socket.io-client-cpp icon indicating copy to clipboard operation
socket.io-client-cpp copied to clipboard
verified publisher icon socketio

build(deps): bump engine.io and socket.io in /test/echo_server

Open dependabot[bot] opened this issue 3 years ago • 0 comments

Bumps engine.io to 4.1.2 and updates ancestor dependency socket.io. These dependencies need to be updated together.

Updates engine.io from 4.0.6 to 4.1.2

Release notes

Sourced from engine.io's releases.

4.1.2

:warning: This release contains an important security fix :warning:

A malicious client could send a specially crafted HTTP request, triggering an uncaught exception and killing the Node.js process:

RangeError: Invalid WebSocket frame: RSV2 and RSV3 must be clear at Receiver.getInfo (/.../node_modules/ws/lib/receiver.js:176:14) at Receiver.startLoop (/.../node_modules/ws/lib/receiver.js:136:22) at Receiver._write (/.../node_modules/ws/lib/receiver.js:83:10) at writeOrBuffer (internal/streams/writable.js:358:12)

This bug was introduced by this commit, included in [email protected], so previous releases are not impacted.

Thanks to Marcus Wejderot from Mevisio for the responsible disclosure.

Bug Fixes

  • properly handle invalid data sent by a malicious websocket client (a70800d)

Links

4.1.1

Bug Fixes

  • do not reset the ping timer after upgrade (ff2b8ab)

Links

4.1.0

Features

  • add support for v3.x clients (663d326)

Links

Changelog

Sourced from engine.io's changelog.

4.1.2 (2022-01-11)

:warning: This release contains an important security fix :warning:

A malicious client could send a specially crafted HTTP request, triggering an uncaught exception and killing the Node.js process:

RangeError: Invalid WebSocket frame: RSV2 and RSV3 must be clear at Receiver.getInfo (/.../node_modules/ws/lib/receiver.js:176:14) at Receiver.startLoop (/.../node_modules/ws/lib/receiver.js:136:22) at Receiver._write (/.../node_modules/ws/lib/receiver.js:83:10) at writeOrBuffer (internal/streams/writable.js:358:12)

This bug was introduced by this commit, included in [email protected], so previous releases are not impacted.

Thanks to Marcus Wejderot from Mevisio for the responsible disclosure.

Bug Fixes

  • properly handle invalid data sent by a malicious websocket client (a70800d)

4.1.1 (2021-02-02)

Bug Fixes

4.1.0 (2021-01-14)

Features

  • add support for v3.x clients (663d326)
Commits
  • c6315af chore(release): 4.1.2
  • a70800d fix: properly handle invalid data sent by a malicious websocket client
  • 9534355 chore(release): 4.1.1
  • ae840fa chore: point towards the master branch for the CI badge
  • ff2b8ab fix: do not reset the ping timer after upgrade
  • e5b307c chore(release): 4.1.0
  • 663d326 feat: add support for v3.x clients
  • See full diff in compare view

Updates socket.io from 3.0.5 to 3.1.2

Release notes

Sourced from socket.io's releases.

3.1.2

Bug Fixes

  • ignore packets received after disconnection (494c64e)

Links:

3.1.1

Bug Fixes

  • properly parse the CONNECT packet in v2 compatibility mode (6f4bd7f)
  • typings: add return types and general-case overload signatures (#3776) (9e8f288)
  • typings: update the types of "query", "auth" and "headers" (4f2e9a7)

Links:

3.1.0

In order to ease the migration to Socket.IO v3, the v3 server is now able to communicate with v2 clients:

const io = require("socket.io")({
  allowEIO3: true // false by default
});

Note: the allowEIO3 refers to the version 3 of the Engine.IO protocol which is used in Socket.IO v2

Features

Bug Fixes

  • allow integers as event names (1c220dd)

... (truncated)

Changelog

Sourced from socket.io's changelog.

3.1.2 (2021-02-26)

Bug Fixes

  • ignore packets received after disconnection (494c64e)

3.1.1 (2021-02-03)

Bug Fixes

  • properly parse the CONNECT packet in v2 compatibility mode (6f4bd7f)
  • typings: add return types and general-case overload signatures (#3776) (9e8f288)
  • typings: update the types of "query", "auth" and "headers" (4f2e9a7)

3.1.0 (2021-01-15)

Features

Bug Fixes

  • allow integers as event names (1c220dd)

2.4.1 (2021-01-07)

Reverts

  • fix(security): do not allow all origins by default (a169050)
Commits
  • 225ade0 chore(release): 3.1.2
  • 494c64e fix: ignore packet received after disconnection
  • 67a61e3 chore: loosen the version requirement of @​types/node
  • 7467216 docs(examples): 4th and final part of the "private messaging" example
  • 7247b40 docs(examples): 3rd part of the "private messaging" example
  • 992c938 docs(examples): 2nd part of the "private messaging" example
  • 8b404f4 docs(examples): 1st part of the "private messaging" example
  • 12221f2 chore(release): 3.1.1
  • 6f4bd7f fix: properly parse the CONNECT packet in v2 compatibility mode
  • 4f2e9a7 fix(typings): update the types of "query", "auth" and "headers"
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

dependabot[bot] avatar Nov 14 '22 12:11 dependabot[bot]