undici WebSocket client vulnerable to denial of service via fragment count bypass
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 6.26.0, 7.28.0, 8.5.0 and 3 more.
Impact: The undici WebSocket client enforces maxPayloadSize on the cumulative byte count of fragments in a message but does not enforce a limit on the number of fragments. A malicious WebSocket server can stream many small or empty continuation frames that each pass per-frame and cumulative-size validation, collectively causing unbounded memory growth in the client process. The result is memory exhaustion and a denial of service. Affected applications are those using the undici WebSocket client (new WebSocket(...)) or the WebSocketStream API that can be induced to connect to an attacker-controlled or compromised WebSocket endpoint. All releases starting at undici 6.17.0 are affected. Patches: Upgrade to undici >= 6.26.0, >= 7.28.0, or >= 8.5.0. Workarounds: No workaround is available. The fix must be applied through an upgrade.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| undici | <6.26.0, >=7.0.0 <7.28.0, >=8.0.0 <8.5.0 | 6.26.0, 7.28.0, 8.5.0 | |
| npm: undici | <6.27.0, >=7.0.0 <7.28.0, >=8.0.0 <8.5.0 | 6.27.0, 7.28.0, 8.5.0 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket