The issue is related to the `SniHandler` class in Netty, which can allocate up to 16MB of heap for each channel during the TLS handshake. This can be exploited to cause a denial of service, potentially leading to an OutOfMemoryError. The `SniHandler` waits for the TLS handshake to configure a `SslHandler` according to the indicated server name by the `ClientHello` record, allocating 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 no checks done here, and it is possible to craft a packet that makes the `SslClientHelloHandler` allocate a large amount of memory.