| Title | netty netty-incubator-codec-quic 0.0.75 Default Token Handler Skips Source-Address Validation |
|---|
| Description | A QUIC server built with QuicServerCodecBuilder and no explicit token handler silently gets NoQuicTokenHandler, whose validateToken() simply returns 0. In the server codec, 0 does not mean “invalid” — it means “token valid, original Destination Connection ID (DCID) starts at offset 0”, so the server passes the packet to quiche_accept as if the client’s source address had already been validated by a Retry round‑trip. I verified the accept/reject branch on a live server. Any off‑path attacker who flips a single arbitrary byte in the token field of a spoofed INITIAL will be treated as address‑validated. The repository is no longer maintained, but many users still rely on it. |
|---|
| Source | ⚠️ https://github.com/August829/CVEP/issues/38 |
|---|
| User | Yu Bao from PayPal Cyber Security Team (UID 99838) |
|---|
| Submission | 09/08/2026 08:30 (2 months ago) |
|---|
| Moderation | 10/11/2026 12:22 (1 month later) |
|---|
| Status | Duplicate |
|---|
| VulDB entry | 370589 [Netty up to 8.0 writeToken verification of source] |
|---|
| Points | 0 |
|---|