Closed renovate[bot] closed 1 year ago
This PR contains the following updates:
6.2.1
6.4.2
Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.
A specially crafted HTTP request can trigger an uncaught exception on the Engine.IO server, thus killing the Node.js process.
TypeError: Cannot read properties of undefined (reading 'handlesUpgrades') at Server.onWebSocket (build/server.js:515:67)
This impacts all the users of the engine.io package, including those who uses depending packages like socket.io.
engine.io
socket.io
A fix has been released today (2023/05/02): 6.4.2
This bug was introduced in version 5.1.0 and included in version 4.1.0 of the socket.io parent package. Older versions are not impacted.
For socket.io users:
socket.io@4.6.x
~6.4.0
npm audit fix
socket.io@4.5.x
~6.2.0
socket.io@4.4.x
~6.1.0
socket.io@4.3.x
~6.0.0
socket.io@4.2.x
~5.2.0
socket.io@4.1.x
~5.1.1
socket.io@4.0.x
~5.0.0
socket.io@3.1.x
~4.1.0
socket.io@3.0.x
~4.0.0
socket.io@2.5.0
~3.6.0
socket.io@2.4.x
~3.5.0
There is no known workaround except upgrading to a safe version.
If you have any questions or comments about this advisory:
Thanks to Thomas Rinsma from Codean for the responsible disclosure.
📅 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 this update again.
This PR has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
6.2.1
->6.4.2
⚠ Dependency Lookup Warnings ⚠
Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.
GitHub Vulnerability Alerts
CVE-2023-31125
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 (2023/05/02): 6.4.2
This bug was introduced in version 5.1.0 and included in version 4.1.0 of the
socket.io
parent package. Older versions are not impacted.For
socket.io
users:engine.io
versionsocket.io@4.6.x
~6.4.0
npm audit fix
should be sufficientsocket.io@4.5.x
~6.2.0
socket.io@4.6.x
socket.io@4.4.x
~6.1.0
socket.io@4.6.x
socket.io@4.3.x
~6.0.0
socket.io@4.6.x
socket.io@4.2.x
~5.2.0
socket.io@4.6.x
socket.io@4.1.x
~5.1.1
socket.io@4.6.x
socket.io@4.0.x
~5.0.0
socket.io@3.1.x
~4.1.0
socket.io@3.0.x
~4.0.0
socket.io@2.5.0
~3.6.0
socket.io@2.4.x
and below~3.5.0
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 Thomas Rinsma from Codean for the responsible disclosure.
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 this update again.
This PR has been generated by Mend Renovate. View repository job log here.