Netty 4.2.0 through 4.2.16 TLS Hostname Verification Bypass
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 4.1.137.Final and 4.2.16.Final.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| netty | <4.1.137.Final, >=4.2.0.Final <4.2.16.Final | 4.1.137.Final, 4.2.16.Final |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket