engine.io-server-java
engine.io-server-java copied to clipboard
Bump engine.io from 5.1.0 to 5.2.1 in /engine.io-server-test/src/test/resources
Bumps engine.io from 5.1.0 to 5.2.1.
Release notes
Sourced from engine.io's releases.
5.2.1
: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 (66f889f)
Links
- Diff: https://github.com/socketio/engine.io/compare/5.2.0...5.2.1
- Client release: -
- ws version: ~7.4.2
5.2.0
No change on the server-side, this matches the client release.
Links
- Diff: https://github.com/socketio/engine.io/compare/5.1.1...5.2.0
- Client release: 5.2.0
- ws version: ~7.4.2
5.1.1
Bug Fixes
- properly close the websocket connection upon handshake error (4360686)
Links
- Diff: https://github.com/socketio/engine.io/compare/5.1.0...5.1.1
- Client release: -
- ws version: ~7.4.2
Changelog
Sourced from engine.io's changelog.
5.2.1 (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 (66f889f)
5.2.0 (2021-08-29)
No change on the server-side, this matches the client release.
5.1.1 (2021-05-16)
Bug Fixes
- properly close the websocket connection upon handshake error (4360686)
Commits
d36199cchore(release): 5.2.166f889ffix: properly handle invalid data sent by a malicious websocket client313ca50chore(release): 5.2.0b9dc43cdocs: add documentation aboutheartbeatevent (#623)7e9e544chore(deps): bump ws from 7.4.2 to 7.4.6 (#621)733ad4dchore(release): 5.1.14360686fix: properly close the websocket connection upon handshake error29bd4fechore(deps): bump lodash from 4.17.20 to 4.17.21 (#619)- See full diff 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill 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 versionwill 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 dependencywill 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 labelswill set the current labels as the default for future PRs for this repo and language@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language@dependabot use this milestonewill 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.