You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Observation
We observed that the aioquic implementation uses a single packet number space for Initial, Handshake, 0-RTT, and 1-RTT packets. While this issue does not result in an immediate vulnerability, it deviates from the standard. According to RFC 9000 (https://www.rfc-editor.org/rfc/rfc9000.html#name-packet-numbers), separate packet number spaces should be used: one for Initial packets, another for Handshake packets, and a third shared space for both 0-RTT and 1-RTT packets.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Tested Build
v1.2.0
Observation
We observed that the aioquic implementation uses a single packet number space for Initial, Handshake, 0-RTT, and 1-RTT packets. While this issue does not result in an immediate vulnerability, it deviates from the standard. According to RFC 9000 (https://www.rfc-editor.org/rfc/rfc9000.html#name-packet-numbers), separate packet number spaces should be used: one for Initial packets, another for Handshake packets, and a third shared space for both 0-RTT and 1-RTT packets.
The text was updated successfully, but these errors were encountered: