Uncaught Exception in engine.io - engine.io

Description

A specially crafted HTTP request can trigger an uncaught exception on the Engine.IO server, thus 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.

Recommendation

Update the engine.io package to the latest compatible version. Followings are version details:

• Affected version(s): **>= 6.0.0, < 6.1.1

  >= 5.0.0, < 5.2.1

  >= 4.0.0, < 4.1.2**

• Patched version(s): **6.1.1

  5.2.1

  4.1.2**

References

• GHSA-273r-mgr4-v34f
• security.netapp.com
• CVE-2022-21676
• CWE-754
• CWE-755
• CAPEC-310
• OWASP 2021-A6

Related Issues

• Uncaught exception in engine.io - CVE-2022-41940
• engine.io Uncaught Exception vulnerability - CVE-2023-31125
• fastify/websocket vulnerable to uncaught exception via crash on malformed packet - CVE-2022-39386
• Uncaught Exception in yaml - CVE-2023-2251

You might also like:

How to Secure your NodeJs Express Javascript Application - part 1

How to Secure your NodeJs Express Javascript Application - part 2

10 Secure Coding Best Practices to Follow in Every Project

Tags:

npm

engine.io