Closed Bug 1860211 Opened 2 years ago Closed 2 years ago

Protocol violation: Neqo server does not close the connection when receiving a packet without any frames.

Categories

(Core :: Networking, enhancement, P2)

Product:
Core
Component:
Networking
Version:
Other Branch
Type:
enhancement

Tracking

()

Status:
RESOLVED MOVED

People

(Reporter: kiankai.ang, Unassigned)

References

(Blocks 1 open bug,
URL
)

Details

(Whiteboard: [necko-triaged][necko-priority-new])

Steps to reproduce:

Packet sequence to replicate the violation:

  1. Client sends an Initial packet carrying a CRYPTO frame with Client Hello.
  2. Client sends a Handshake packet without any frames.

Actual results:

Violation detail:
Neqo server does not close the connection immediately after receiving a packet containing no frames.

Expected results:

According to Section 12.4, RFC 9000, an endpoint MUST treat receipt of a packet containing no frames as a connection error of type PROTOCOL_VIOLATION. Violations of the protocol lead to an immediate close.

Blocks: QUIC
Severity: -- → S3
Priority: -- → P2
Whiteboard: [necko-triaged][necko-priority-new]

I opened an issue for this in the neqo repo:
https://github.com/mozilla/neqo/issues/1476

URL: https://github.com/mozilla/neqo/issue...
Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → MOVED
You need to log in before you can comment on or make changes to this bug.