Resource Exhaustion Affecting netty-tcnative package, versions <2.0.61-150200.3.13.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.12% (47th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Resource Exhaustion vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-SLES155-NETTYTCNATIVE-5808290
  • published27 Jul 2023
  • disclosed26 Jul 2023

Introduced: 26 Jul 2023

CVE-2023-34462  (opens in a new tab)
CWE-400  (opens in a new tab)

How to fix?

Upgrade SLES:15.5 netty-tcnative to version 2.0.61-150200.3.13.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream netty-tcnative package and not the netty-tcnative package as distributed by SLES. See How to fix? for SLES:15.5 relevant fixed versions and status.

Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients. 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. 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. This vulnerability has been fixed in version 4.1.94.Final.

CVSS Scores

version 3.1