undicis experimental WebSocketStream client crashes the whole Node.js process when a remote peer closes the TCP connection without a WebSocket close handshake. On an unclean close the internal socket-close handler calls abort on the writable stream unconditionally and discards the returned promise, but per the WHATWG Streams standard aborting a locked writable returns a promise that rejects with a TypeError. Because the application holds a writer on that writable, which is the only way to write, the rejection is never observed and Nodes default unhandled-rejection behavior terminates the process. An untrusted server can therefore crash a client with a single abrupt disconnect, with no authentication and no application mistake. This affects undici versions from 7.0.0 up to 7.29.1 and from 8.0.0 up to 8.10.2. Users should upgrade to undici 7.29.1 or 8.10.2.
Weakness
An exception is thrown from a function, but it is not caught.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Undici | Nodejs | 7.0.0 (including) | 7.29.1 (excluding) |
| Undici | Nodejs | 8.0.0 (including) | 8.10.2 (excluding) |
| Red Hat Hardened Images | RedHat | nodejs26-main-11.19.0-1.26.7.0.1.5.2.hum1 | * |
| Red Hat Hardened Images | RedHat | nodejs26-main-26.7.0-1.5.2.hum1 | * |
| Red Hat Hardened Images | RedHat | nodejs24-main-11.16.0-1.24.18.1.0.2.2.hum1 | * |
| Red Hat Hardened Images | RedHat | nodejs24-main-24.18.1-0.2.2.hum1 | * |
| Red Hat Hardened Images | RedHat | grafana12-4-main-12.4.10-0.2.hum1 | * |
| Node-undici | Ubuntu | upstream | * |