Netty
Netty 4.2.0 through 4.2.16 TLS Hostname Verification Bypass
Netty (io.netty:netty-handler) versions from 4.2.0.Final through 4.2.16.Final and versions through 4.1.136.Final disable TLS hostname verification on the SslProvider.OPENSSL client path when a plain (non-extended) X509TrustManager is used and Unsafe-based trust-manager wrapping is unavailable (Java 25+). In this configuration the OpenSSL client does not perform hostname verification, allowing a man-in-the-middle attacker to present a certificate issued for a different hostname that is accepted without validation. Fixed in 4.2.17.Final and 4.1.137.Final.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 4.2.0.Final, < 4.2.16.Final
Fixed in 4.2.16.Final
- < 4.1.137.Final
Fixed in 4.1.137.Final
Mitigation
Upgrade netty to 4.2.16.Final or later.
Upgrade netty to 4.1.137.Final or later.
References
- Vendor advisory github.com/netty/netty/security/advisories/GHS…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.