Bzip2Decoder doesn't allow setting size restrictions for decompressed data
The Netty project Netty
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| io.netty:netty-codec Maven |
|
|
| org.jboss.netty:netty Maven |
| No fix yet |
| io.netty:netty Maven |
|
The Netty project Netty
| Product | Affected | Fixed in |
|---|---|---|
| io.netty:netty-codec Maven |
|
|
| org.jboss.netty:netty Maven |
| No fix yet |
| io.netty:netty Maven |
|
| No fix yet |
The Bzip2 decompression decoder function doesn't 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
From the CVE record · JFROG
Netty's Bzip2Decoder does not limit decompressed output size, affecting all users of the decoder. An attacker who can supply malicious Bzip2 input for decoding can trigger an out-of-memory error and cause a denial of service. The input does not specify whether network access, authentication, or user interaction is required.
Engineers using Maven io.netty:netty-codec before 4.1.68.Final, or org.jboss.netty:netty or io.netty:netty at any version, should check their use of Bzip2Decoder.