Netty's Default QUIC token handler accepts any client-supplied token

Summary

Netty is a network application framework for development of protocol servers and clients. NoQuicTokenHandler is the tokenHandler used when the application does not set one. Prior to version 4.2.15.Final, its writeToken() returns false (server will not send Retry — acceptable), but validateToken() unconditionally `return 0`. In QuicheQuicServerCodec.handlePacket(), a non-negative return from validateToken() is interpreted as 'token is valid, ODCID starts at offset 0', causing the server to call quiche_accept as if the client's address had been validated by a Retry round-trip. Per RFC 9000 §8.1, a validated address lifts the 3× anti-amplification send limit. Thus any attacker who includes ANY non-empty token bytes in an Initial packet — with a spoofed victim source IP — causes the Netty server to treat the victim as validated and reflect full-size handshake flights (certificates, etc.) toward it without the 3× cap. The correct 'no token handler' semantics would be to return -1 (invalid) so the normal un-validated path and amplification limit apply. Version 4.2.15.Final patches the issue.

Timeline

1. Jun 12, 2026, 2:06 PM UTCCVE published
2. Jun 13, 2026, 3:03 AM UTCCISA SSVC assessment

   Exploitation: none · Automatable: yes · Technical impact: partial

3. Jul 15, 2026, 12:53 AM UTCRecord last updated

Affected versions

• netty netty

  From 4.2.0.Final · fixed in 4.2.15.Final

• io.netty:netty-codec-classes-quicMaven

  From 4.2.0.Final · fixed in 4.2.15.Final

References 2