AIKIDO-2026-563243
netty-codec-classes-quic is vulnerable to Improper Certificate Validation
75
High Risk
This Affects:
netty-codec-classes-quicTL;DR
When a QUIC client is configured with a plain X509TrustManager rather than an extended, engine-aware one, the BoringSSL verify callback invokes only the two-argument checkServerTrusted(chain, authType) overload, discarding the QuicheQuicSslEngine that carries the peer host and SSL parameters. Endpoint identification is therefore never enforced and a certificate valid for the wrong hostname is accepted. The fix requires an X509ExtendedTrustManager when endpoint identification is enabled, so hostname validation is applied during the handshake.
Who does this affect?
You are affected if you are using a version that falls within the vulnerable range and you use the QUIC client with a plain X509TrustManager.
Background info
netty-codec-classes-quic is vulnerable to Improper Certificate Validation in versions 4.2.11.Final - 4.2.17.Final.
How to fix this
Upgrade the io.netty:netty-codec-classes-quic library to the patch version.
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.