netty-handler is vulnerable to Improper Check for Unusual or Exceptional Conditions
91
Critical Risk
Netty contains a vulnerability in TLS ClientHello parsing that can cause the server to select the default SslContext instead of the intended SNI-specific one. In deployments that rely solely on SNI-selected SslContexts to enforce mutual TLS (mTLS), where the default context does not require client certificates and no application-layer certificate validation is performed, a remote attacker may be able to bypass the client certificate requirement for protected routes. Applications that do not use SNI-based SslContext selection, require client certificates in the default context as well, or perform independent certificate validation are not affected.
You are affected if you are using a version that falls within the vulnerable range and you rely on SNI-selected SslContexts to enforce mutual TLS (mTLS), where the default SslContext does not require client certificates and no application-layer certificate validation is performed.
netty-handler is vulnerable to Improper Check for Unusual or Exceptional Conditions in versions 0.0.0 - 4.1.136.Final and 4.2.0.Final - 4.2.16.Final.
Upgrade the io.netty:netty-handler library to the patch version.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.