Netty: Lz4FrameDecoder resource exhaustion
netty · io.netty netty-codec · io.netty netty-codec-compression
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| io.netty:netty-codec-compression Maven |
|
|
| io.netty:netty-codec Maven |
|
|
netty · io.netty netty-codec · io.netty netty-codec-compression
| Product | Affected | Fixed in |
|---|---|---|
| io.netty:netty-codec-compression Maven |
|
|
| io.netty:netty-codec Maven |
|
|
Netty is an asynchronous, event-driven network application framework. Prior to 4.2.13.Final and 4.1.133.Final, Lz4FrameDecoder allocates a ByteBuf of size decompressedLength (up to 32 MB per block) before LZ4 runs. A peer only needs a 21-byte header plus compressedLength payload bytes - 22 bytes if compressedLength == 1 - to force that allocation. This vulnerability is fixed in 4.2.13.Final and 4.1.133.Final.
From the CVE record · GitHub_M
Netty's Lz4FrameDecoder allocates a buffer of up to 32 MB per block before LZ4 decompression runs. A network peer can trigger that allocation with a 21-byte header and a compressed payload as small as one byte.
Engineers using Maven io.netty:netty-codec-compression before 4.2.13.Final or io.netty:netty-codec before 4.1.133.Final should check their dependencies.