Description
Netty is an asynchronous, event-driven network application framework. Prior to 4.2.13.Final and 4.1.133.Final, HttpContentDecompressor accepts a maxAllocation parameter to limit decompression buffer size and prevent decompression bomb attacks. This limit is correctly enforced for gzip and deflate encodings via ZlibDecoder, but is silently ignored when the content encoding is br (Brotli), zstd, or snappy. An attacker can bypass the configured decompression limit by sending a compressed payload with Content-Encoding: br instead of Content-Encoding: gzip, causing unbounded memory allocation and out-of-memory denial of service. The same vulnerability exists in DelegatingDecompressorFrameListener for HTTP/2 connections. This vulnerability is fixed in 4.2.13.Final and 4.1.133.Final.
CVSS breakdown
Affected products
- io.netty / netty-codec-http>= 4.2.0.Alpha1, < 4.2.13.Final – >= 4.2.0.Alpha1, < 4.2.13.Final
- io.netty / netty-codec-http< 4.1.133.Final – < 4.1.133.Final
- io.netty / netty-codec-http2>= 4.2.0.Alpha1, < 4.2.13.Final – >= 4.2.0.Alpha1, < 4.2.13.Final
- io.netty / netty-codec-http2< 4.1.133.Final – < 4.1.133.Final
- netty / netty>= 4.2.0.Alpha1, < 4.2.13.Final – >= 4.2.0.Alpha1, < 4.2.13.Final
- netty / netty< 4.1.133.Final – < 4.1.133.Final