dependencies: Update dependency engine.io to 6.2.1 [SECURITY] - abandoned #308
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
6.1.0
->6.2.1
GitHub Vulnerability Alerts
CVE-2022-21676
Impact
A specially crafted HTTP request can trigger an uncaught exception on the Engine.IO server, thus killing the Node.js process.
This impacts all the users of the
engine.io
package starting from version4.0.0
, including those who uses depending packages likesocket.io
.Patches
A fix has been released for each major branch:
[email protected]
4.1.2
[email protected]
5.2.1
[email protected]
6.1.1
Previous versions (
< 4.0.0
) are not impacted.For
socket.io
users:engine.io
version[email protected]
~6.1.0
[email protected]
~6.0.0
[email protected]
[email protected]
~5.2.0
[email protected]
~5.1.1
[email protected]
[email protected]
~5.0.0
[email protected]
[email protected]
~4.1.0
[email protected]
~4.0.0
[email protected]
or[email protected]
(see here)In most cases, running
npm audit fix
should be sufficient. You can also usenpm update engine.io --depth=9999
.Workarounds
There is no known workaround except upgrading to a safe version.
For more information
If you have any questions or comments about this advisory:
engine.io
Thanks to Marcus Wejderot from Mevisio for the responsible disclosure.
CVE-2022-41940
Impact
A specially crafted HTTP request can trigger an uncaught exception on the Engine.IO server, thus killing the Node.js process.
This impacts all the users of the
engine.io
package, including those who uses depending packages likesocket.io
.Patches
A fix has been released today (2022/11/20):
[email protected]
3.6.1
[email protected]
6.2.1
For
socket.io
users:engine.io
version[email protected]
~6.2.0
npm audit fix
should be sufficient[email protected]
~6.1.0
[email protected]
[email protected]
~6.0.0
[email protected]
[email protected]
~5.2.0
[email protected]
[email protected]
~5.1.1
[email protected]
[email protected]
~5.0.0
[email protected]
[email protected]
~4.1.0
[email protected]
(see here)[email protected]
~4.0.0
[email protected]
(see here)[email protected]
~3.6.0
npm audit fix
should be sufficient[email protected]
and below~3.5.0
[email protected]
Workarounds
There is no known workaround except upgrading to a safe version.
For more information
If you have any questions or comments about this advisory:
engine.io
Thanks to Jonathan Neve for the responsible disclosure.
Configuration
📅 Schedule: Branch creation - "" in timezone Europe/Berlin, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.