Improper Verification of Cryptographic Signature Affecting netty-tcnative package, versions <2.0.79-150200.3.45.1


Severity

Recommended
0.0
high
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.27% (19th 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 IDSNYK-SLES155-NETTYTCNATIVE-17928637
  • published10 Jul 2026
  • disclosed8 Jul 2026

Introduced: 8 Jul 2026

NewCVE-2026-50010  (opens in a new tab)
CWE-347  (opens in a new tab)

How to fix?

Upgrade SLES:15.5 netty-tcnative to version 2.0.79-150200.3.45.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 a network application framework for development of protocol servers and clients. Prior to versions 4.1.135.Final and 4.2.15.Final, SimpleTrustManagerFactory.engineGetTrustManagers() and related paths wrap any user-supplied plain X509TrustManager in X509TrustManagerWrapper, which extends X509ExtendedTrustManager but implements the 3-arg checkServerTrusted(chain, authType, SSLEngine) by discarding the SSLEngine and calling the 2-arg delegate. Because the object now IS an X509ExtendedTrustManager, neither SunJSSE's internal AbstractTrustManagerWrapper nor Netty's own OpenSslX509TrustManagerWrapper will re-wrap it to add endpoint-identification. Consequently, even though Netty 4.2 sets endpointIdentificationAlgorithm="HTTPS" by default, a client built with SslContextBuilder.forClient().trustManager(somePlainX509TrustManager) performs no hostname verification at all. Versions 4.1.135.Final and 4.2.15.Final patch the issue.

CVSS Base Scores

version 3.1