Netty Bzip2Decoder: Infinite Loop in RLE State Machine Leads to Event-Loop Thread Hang
netty
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| io.netty:netty-codec-compression Maven |
|
|
| io.netty:netty-codec Maven |
|
|
netty
| 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 versions 4.1.136.Final and 4.2.16.Final, the `Bzip2Decoder` handler in Netty's compression codec pipeline is vulnerable to a denial-of-service attack through a malformed bzip2 stream that permanently captures the event-loop thread in an infinite loop. The vulnerability exists in the run-length encoding (RLE) state machine within [`Bzip2BlockDecompressor.read()`]. This issue has been fixed in versions 4.1.136.Final and 4.2.16.Final.
From the CVE record · GitHub_M
Netty's Bzip2Decoder can enter an infinite loop when it processes a malformed bzip2 stream, permanently occupying an event-loop thread and causing a denial of service. The input does not specify whether exploitation requires network access, authentication, or user interaction.
Check applications using Maven io.netty:netty-codec-compression versions >=4.2.0.Final and <4.2.16.Final, or io.netty:netty-codec versions <4.1.136.Final.