Описание
Uncaught exception in engine.io
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 like socket.io.
Patches
A fix has been released today (2022/11/20):
| Version range | Fixed version |
|---|---|
engine.io@3.x.y | 3.6.1 |
engine.io@6.x.y | 6.2.1 |
For socket.io users:
| Version range | engine.io version | Needs minor update? |
|---|---|---|
socket.io@4.5.x | ~6.2.0 | npm audit fix should be sufficient |
socket.io@4.4.x | ~6.1.0 | Please upgrade to socket.io@4.5.x |
socket.io@4.3.x | ~6.0.0 | Please upgrade to socket.io@4.5.x |
socket.io@4.2.x | ~5.2.0 | Please upgrade to socket.io@4.5.x |
socket.io@4.1.x | ~5.1.1 | Please upgrade to socket.io@4.5.x |
socket.io@4.0.x | ~5.0.0 | Please upgrade to socket.io@4.5.x |
socket.io@3.1.x | ~4.1.0 | Please upgrade to socket.io@4.5.x (see here) |
socket.io@3.0.x | ~4.0.0 | Please upgrade to socket.io@4.5.x (see here) |
socket.io@2.5.0 | ~3.6.0 | npm audit fix should be sufficient |
socket.io@2.4.x and below | ~3.5.0 | Please upgrade to socket.io@2.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:
- Open an issue in
engine.io
Thanks to Jonathan Neve for the responsible disclosure.
Ссылки
Пакеты
engine.io
< 3.6.1
3.6.1
engine.io
>= 4.0.0, < 6.2.1
6.2.1
Связанные уязвимости
Engine.IO is the implementation of transport-based cross-browser/cross-device bi-directional communication layer for Socket.IO. 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 like socket.io. There is no known workaround except upgrading to a safe version. There are patches for this issue released in versions 3.6.1 and 6.2.1.
Engine.IO is the implementation of transport-based cross-browser/cross-device bi-directional communication layer for Socket.IO. 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 like socket.io. There is no known workaround except upgrading to a safe version. There are patches for this issue released in versions 3.6.1 and 6.2.1.