Netty HttpPostRequestDecoder can OOM
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 5.3epss 1.4%
exploitation probability
1.4%top 29% of all CVEs
observed exploitation
nono source reports it
In short
Netty's HttpPostRequestDecoder can be forced to consume excessive memory when processing HTTP POST requests with many small form fields, causing an application to run out of memory and crash.
Technical detail
The HttpPostRequestDecoder lacks limits on the number of form fields and the size of accumulated data in the undecodedChunk buffer, allowing an attacker to send chunked POST requests with numerous small fields that accumulate in bodyListHttpData without bounds, leading to unbounded memory consumption and potential denial of service.
Summary generated and translated by AI from the official description.
Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients. The `HttpPostRequestDecoder` can be tricked to accumulate data. While the decoder can store items on the disk if configured so, there are no limits to the number of fields the form can have, an attacher can send a chunked post consisting of many small fields that will be accumulated in the `bodyListHttpData` list. The decoder cumulates bytes in the `undecodedChunk` buffer until it can decode a field, this field can cumulate data without limits. This vulnerability is fixed in 4.1.108.Final.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Affected products
netty · netty