fastify-websocket vulnerable to uncaught exception via crash on malformed packet
fastify-websocket
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @fastify/websocket npm |
|
|
| fastify-websocket npm |
| No fix yet |
fastify-websocket
| Product | Affected | Fixed in |
|---|---|---|
| @fastify/websocket npm |
|
|
| fastify-websocket npm |
| No fix yet |
@fastify/websocket provides WebSocket support for Fastify. Any application using @fastify/websocket could crash if a specific, malformed packet is sent. All versions of fastify-websocket are also impacted. That module is deprecated, so it will not be patched. This has been patched in version 7.1.1 (fastify v4) and version 5.0.1 (fastify v3). There are currently no known workarounds. However, it should be possible to attach the error handler manually. The recommended path is upgrading to the patched versions.
From the CVE record · GitHub_M
Applications using affected @fastify/websocket versions can crash when an attacker sends a specific malformed packet over the network. The deprecated fastify-websocket package is also affected and will not be patched. The input does not specify whether authentication or user interaction is required.
Check applications using npm @fastify/websocket versions >=5.0.0 <5.0.1 or >=6.0.0 <7.1.1, or npm fastify-websocket versions <=4.3.0.