Null Byte Interaction Error (Poison Null Byte) Affecting netty-tcnative package, versions <2.0.84-150200.3.51.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.25% (16th 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-SLES156-NETTYTCNATIVE-20305742
  • published30 Sept 2026
  • disclosed29 Sept 2026

Introduced: 29 Sep 2026

NewCVE-2026-62380  (opens in a new tab)
CWE-626  (opens in a new tab)

How to fix?

Upgrade SLES:15.6 netty-tcnative to version 2.0.84-150200.3.51.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.6 relevant fixed versions and status.

Netty (io.netty:netty-codec-socks) versions 4.2.0.Final through 4.2.16.Final and 4.1.x through 4.1.136.Final contain null byte, CRLF, and credential injection vulnerabilities in the SOCKS4 (Socks4ClientEncoder) and SOCKS5 (Socks5ClientEncoder) client encoders, which fail to validate domain address and authentication (username/password) fields. An attacker able to control these fields can inject null bytes or CRLF characters to truncate or alter values, potentially enabling domain spoofing, SOCKS4 userid truncation, authentication data injection, and protocol confusion. Fixed in 4.2.17.Final and 4.1.137.Final.

CVSS Base Scores

version 3.1