VulnerableCode Package Details - pkg:maven/io.netty/netty-all@4.0.12.Final

Search for packages

Vulnerability	Summary	Fixed by
VCID-abq9-s6ra-m3gv Aliases: CVE-2022-41881 GHSA-fx2c-96vj-985v	Netty project is an event-driven asynchronous network application framework. In versions prior to 4.1.86.Final, a StackOverflowError can be raised when parsing a malformed crafted message due to an infinite recursion. This issue is patched in version 4.1.86.Final. There is no workaround, except using a custom HaProxyMessageDecoder.	4.1.86 Affected by 0 other vulnerabilities. 4.1.86.Final Affected by 1 other vulnerability. This version is affected by these other vulnerabilities: {{ fixed_by_vuln.vulnerability_id }}
VCID-aju4-13wq-j3az Aliases: CVE-2023-34462 GHSA-6mjq-h674-j845	netty-handler SniHandler 16MB allocation ### Summary The `SniHandler` can allocate up to 16MB of heap for each channel during the TLS handshake. When the handler or the channel does not have an idle timeout, it can be used to make a TCP server using the `SniHandler` to allocate 16MB of heap. ### Details The `SniHandler` class is a handler that waits for the TLS handshake to configure a `SslHandler` according to the indicated server name by the `ClientHello` record. For this matter it allocates a `ByteBuf` using the value defined in the `ClientHello` record. Normally the value of the packet should be smaller than the handshake packet but there are not checks done here and the way the code is written, it is possible to craft a packet that makes the `SslClientHelloHandler` 1/ allocate a 16MB `ByteBuf` 2/ not fail `decode` method `in` buffer 3/ get out of the loop without an exception The combination of this without the use of a timeout makes easy to connect to a TCP server and allocate 16MB of heap memory per connection. ### Impact If the user has no idle timeout handler configured it might be possible for a remote peer to send a client hello packet which lead the server to buffer up to 16MB of data per connection. This could lead to a OutOfMemoryError and so result in a DDOS.	4.1.94.Final Affected by 0 other vulnerabilities.
VCID-tdp2-ve8k-zbds Aliases: CVE-2021-37136 GHSA-grg4-wf29-r9vv	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	4.1.68.Final Affected by 2 other vulnerabilities. This version is affected by these other vulnerabilities: {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} 4.1.68 Affected by 0 other vulnerabilities.

Vulnerability

Summary

Fixed by

VCID-abq9-s6ra-m3gv
Aliases:
CVE-2022-41881
GHSA-fx2c-96vj-985v

Netty project is an event-driven asynchronous network application framework. In versions prior to 4.1.86.Final, a StackOverflowError can be raised when parsing a malformed crafted message due to an infinite recursion. This issue is patched in version 4.1.86.Final. There is no workaround, except using a custom HaProxyMessageDecoder.

4.1.86
Affected by 0 other vulnerabilities.

4.1.86.Final
Affected by 1 other vulnerability.

VCID-aju4-13wq-j3az
Aliases:
CVE-2023-34462
GHSA-6mjq-h674-j845

netty-handler SniHandler 16MB allocation ### Summary The `SniHandler` can allocate up to 16MB of heap for each channel during the TLS handshake. When the handler or the channel does not have an idle timeout, it can be used to make a TCP server using the `SniHandler` to allocate 16MB of heap. ### Details The `SniHandler` class is a handler that waits for the TLS handshake to configure a `SslHandler` according to the indicated server name by the `ClientHello` record. For this matter it allocates a `ByteBuf` using the value defined in the `ClientHello` record. Normally the value of the packet should be smaller than the handshake packet but there are not checks done here and the way the code is written, it is possible to craft a packet that makes the `SslClientHelloHandler` 1/ allocate a 16MB `ByteBuf` 2/ not fail `decode` method `in` buffer 3/ get out of the loop without an exception The combination of this without the use of a timeout makes easy to connect to a TCP server and allocate 16MB of heap memory per connection. ### Impact If the user has no idle timeout handler configured it might be possible for a remote peer to send a client hello packet which lead the server to buffer up to 16MB of data per connection. This could lead to a OutOfMemoryError and so result in a DDOS.

4.1.94.Final
Affected by 0 other vulnerabilities.

VCID-tdp2-ve8k-zbds
Aliases:
CVE-2021-37136
GHSA-grg4-wf29-r9vv

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

4.1.68.Final
Affected by 2 other vulnerabilities.

4.1.68
Affected by 0 other vulnerabilities.

Vulnerability	Summary	Aliases
This package is not known to fix vulnerabilities.

Vulnerability

Summary

Aliases

This package is not known to fix vulnerabilities.

Date	Actor	Action	Vulnerability	Source	VulnerableCode Version
2025-07-03T18:45:59.490275+00:00	GitLab Importer	Affected by	VCID-aju4-13wq-j3az	https://gitlab.com/gitlab-org/advisories-community/-/blob/main/maven/io.netty/netty-all/CVE-2023-34462.yml	37.0.0
2025-07-03T18:36:05.133162+00:00	GitLab Importer	Affected by	VCID-abq9-s6ra-m3gv	https://gitlab.com/gitlab-org/advisories-community/-/blob/main/maven/io.netty/netty-all/CVE-2022-41881.yml	37.0.0
2025-07-03T18:05:49.146204+00:00	GitLab Importer	Affected by	VCID-tdp2-ve8k-zbds	https://gitlab.com/gitlab-org/advisories-community/-/blob/main/maven/io.netty/netty-all/CVE-2021-37136.yml	37.0.0