Medium

netty-handler SniHandler 16MB allocation

  • Disclosed: 20.06.2023
  • Updated: 11.10.2026 13:20

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.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Java / Kotlin (Maven) io.netty:netty-handler < 4.1.94.Final 4.1.94.Final

References

CVSS score 6.5/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness (CWE)
CWE-400, CWE-770
Platform
Java / Kotlin (Maven)
Package
io.netty:netty-handler
Disclosed
20.06.2023
Updated
11.10.2026 13:20

Sources and licenses

OSV / GitHub Advisory Database - GHSA-6mjq-h674-j845 - CC BY 4.0

Vulnerability history: io.netty:netty-handler

All published vulnerabilities of this package (Java / Kotlin (Maven)), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (12) in the archive
Total entries
12
First → latest
02.2020 09.2026
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • Critical 1
  • High 7
  • Medium 4

Disclosures per year

  1. 2020: 4
  2. 2021: 0
  3. 2022: 1
  4. 2023: 1
  5. 2024: 0
  6. 2025: 1
  7. 2026: 5
Severity:
  1. Critical CVE-2026-75595 >= 4.2.0.Final, < 4.2.17.Final, < 4.1.137.Final 4.2.17.Final, 4.1.137.Final
  2. High · 7.5 CVE-2026-50010 >= 4.2.0.Final, < 4.2.15.Final, < 4.1.135.Final 4.2.15.Final, 4.1.135.Final
  3. High · 7.5 CVE-2026-45416 >= 4.2.0.Final, < 4.2.15.Final, < 4.1.135.Final 4.2.15.Final, 4.1.135.Final
  4. High · 8.1 CVE-2026-44249 >= 4.2.0.Final, < 4.2.15.Final, < 4.1.135.Final 4.2.15.Final, 4.1.135.Final
  5. High · 7.5 CVE-2025-24970 >= 4.1.91.Final, < 4.1.118.Final 4.1.118.Final
  6. netty-handler SniHandler 16MB allocation this entry
    Medium · 6.5 CVE-2023-34462 < 4.1.94.Final 4.1.94.Final
  7. High · 7.5 CVE-2016-4970 >= 4.0.0.Alpha1, < 4.0.37.Final, >= 4.1.0.Beta1, < 4.1.1.Final 4.0.37.Final, 4.1.1.Final
  8. High · 7.5 CVE-2020-11612 >= 4.1.0, < 4.1.46 4.1.46
  9. High · 7.5 CVE-2020-7238 >= 4.1.43, < 4.1.45 4.1.45

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.