Package Instance

Uncontrolled Resource Consumption
The Bzip2 decompression decoder function does not allow setting size restrictions on the decompressed output data (which affects the allocation size used during decompression). All users of Bzip2Decoder are affected. The malicious input can trigger an OOME and so a DoS attack

Netty's decoders vulnerable to DoS via zip bomb style attack
With specially crafted input, `BrotliDecoder` and some other decompressing decoders will allocate a large number of reachable byte buffers, which can lead to denial of service.

Uncontrolled Resource Consumption
The Snappy frame decoder function does not restrict the chunk length which may lead to excessive memory usage. Beside this it also may buffer reserved skippable chunks until the whole chunk was received which may lead to excessive memory usage as well. This vulnerability can be triggered by supplying malicious input that decompresses to a very big size (via a network stream or a file) or by sending a huge skippable chunk.

Inconsistent Interpretation of HTTP Requests (HTTP Request Smuggling)
If a `Content-Length` header is present in the original `HTTP/2` request, the field is not validated by `Http2MultiplexHandler` as it is propagated up.