Impact: The undici WebSocket client enforces maxPayloadSize per-frame but does not enforce the cumulative size of fragmented uncompressed messages. A malicious WebSocket server can stream many small fragments that each pass per-frame validation but collectively exceed the configured limit, 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(...)) that can be induced to connect to an attacker-controlled or compromised WebSocket endpoint. This is a regression specific to undici 8.1.0. The 6.25.0 line shipped the equivalent cumulative check from the start and is unaffected. The 7.x line never had the maxPayloadSize feature and is also unaffected. Patches: Upgrade to undici >= 8.5.0. Workarounds: No workaround is available. The fix must be applied through an upgrade.
oryginał ENCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HNode.js Undici
APPNodejs8.0.0 – 8.5.0 (bez)
Powiązane podatności
Impact: undici's ProxyAgent silently drops the requestTls option when configured with a SOCKS5 proxy URI (sock...
Impact: When using Socks5ProxyAgent, undici reuses a single connection pool across different origins without v...
Impact: The undici WebSocket client enforces maxPayloadSize on the cumulative byte count of fragments in a mes...
ImpactA server can reply with a WebSocket frame using the 64-bit length form and an extremely large length. un...
The undici WebSocket client is vulnerable to a denial-of-service attack via unbounded memory consumption durin...