Nodejs undici any version

`undici.request` vulnerable to SSRF using absolute URL on `pathname`

undici is vulnerable to Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')

undici vulnerable to cross-user information disclosure and parse-time crash via degenerate private cache directives

undici vulnerable to TLS certificate validation bypass via dropped connect options in BalancedPool

undici vulnerable to cross-origin request routing via SOCKS5 proxy pool reuse

undici vulnerable to cross-user cookie disclosure via Set-Cookie caching in shared caches

Undici vulnerable to Regular Expression Denial of Service in Headers

undici is vulnerable to Unbounded Memory Consumption in undici WebSocket permessage-deflate Decompression

undici is vulnerable to Unhandled Exception in undici WebSocket Client Due to Invalid server_max_window_bits Validation

undici WebSocket client vulnerable to denial of service via fragment count bypass

undici is vulnerable to Malicious WebSocket 64-bit length overflows undici parser and crashes the client

Undici has an unbounded decompression chain in HTTP responses on Node.js Fetch API via Content-Encoding leads to resource exhaustion

undici WebSocket client vulnerable to denial of service via cumulative fragment bypass

undici vulnerable to Denial of Service via unrequested WebSocket subprotocol

undici vulnerable to Denial of Service via WebSocketStream unclean close

undici vulnerable to cross-user information disclosure via whitespace around equals in Cache-Control directives

undici vulnerable to TLS certificate validation bypass via dropped requestTls in SOCKS5 ProxyAgent

undici vulnerable to cross-origin cache poisoning via missing origin isolation in interceptors

CRLF injection in request headers

CRLF Injection in Nodejs ‘undici’ via host

Uncleared cookies on cross-host/cross-origin redirect in undici

Backpressure request ignored in fetch() in Undici

`Undici.ProxyAgent` never verifies the remote server's certificate, and always exposes all request & response data to the proxy. This unexpectedly means that proxies can MitM all HTTPS traffic, and if the proxy's URL is HTTP then it also means that nominally HTTPS requests are actually sent via plain-text HTTP between Undici and the proxy server.

undici vulnerable to cookie attribute injection via unsanitized domain and unparsed setCookie fields

undici vulnerable to downstream response desynchronization via retry interceptor

undici is vulnerable to Unbounded Memory Consumption in in Undici's DeduplicationHandler via Response Buffering leads to DoS

undici vulnerable to cross-user information disclosure via shared cache whitespace bypass

undici vulnerable to Denial of Service via orphaned RetryHandler response body

undici vulnerable to HTTP header injection via Set-Cookie percent-decoding

undici vulnerable to Denial of Service via unhandled error in WebSocket permessage-deflate decompression

undici vulnerable to Denial of Service via unbounded decompression of compressed responses

undici vulnerable to CRLF Injection via blob-like body 'type' property

CRLF Injection in Nodejs ‘undici’ via Content-Type

undici vulnerable to response truncation via oversized chunked responses in the dump interceptor

undici vulnerable to caching and replay of unsafe HTTP method responses

undici is vulnerable to CRLF Injection via upgrade option

Proxy-Authorization header not cleared on cross-origin redirect in fetch in Undici

Undici's Proxy-Authorization header not cleared on cross-origin redirect for dispatch, request, stream, pipeline

Undici's cookie header not cleared on cross-origin redirect in fetch

undici vulnerable to downstream response splitting via retry interceptor