Medium [CVE-2026-62380] Null byte and CRLF injection in SOCKS client encoders can lead to domain spoofing
This medium-severity Red Hat Linux advisory covers CVE-2026-62380 affecting Exploit Intelligence, OpenShift Serverless, Red Hat AMQ Broker 7.
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
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.
This vulnerability allows a remote attacker to inject null bytes or Carriage Return Line Feed (CRLF) characters into domain address and authentication fields due to insufficient validation. Red Hat severity: Moderate — CVSS 5.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N).
Weakness: CWE-93.
Affected products named by the advisory: Exploit Intelligence; OpenShift Serverless; Red Hat AMQ Broker 7; Red Hat build of Apache Camel 4 for Quarkus 3; and 14 more.
- 4.2.0
- 4.2.16
- 4.1.136
Official advisory · high-confidence parse· fetched 59 minutes ago·verify at source
- 4.2.17
- 4.1.137
Official advisory · high-confidence parse· fetched 59 minutes ago·verify at source
Mitigation checklist
- Applications utilizing Netty's SOCKS client encoders should implement robust input validation and sanitization for all domain address and authentication credential fields. If SOCKS proxy client functionality is not required by the application, it should be disabled to remove the attack surface.
Official advisory · high-confidence parse· fetched 59 minutes ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.