Skip to content

denial-of-service via panic on unreachable code in neqo-transport/src/addr_valid.rs

High
larseggert published GHSA-56c6-rfrf-rh4r Jul 10, 2025

Package

cargo neqo (Rust)

Affected versions

<=0.14.0

Patched versions

>0.14.0

Description

Summary

A remote attacker can trigger a panic in the QUIC server by sending an unauthorized NEW_TOKEN frame as a QUIC client, leading to a denial-of-service vulnerability.

Details

If the QUIC server receives a NEW_TOKEN frame in a 1-RTT packet after the handshake has been completed, it panics instead of handling the protocol violation gracefully. According to the QUIC specification, the server should respond with an appropriate connection close error when receiving illegal frames at this stage.

The panic occurs at neqo-transport/src/addr_valid.rs#L336.

PoC

  1. Establish a QUIC connection and complete the handshake.
  2. Send a 1-RTT packet containing a NEW_TOKEN frame, which is not allowed at this stage.
  3. The server will panic.

Impact

This is a denial-of-service vulnerability. Any client or attacker capable of sending crafted QUIC packets can trigger a panic in Neqo, which crashes the server and results in service unavailability.

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CVE ID

No known CVE

Weaknesses

No CWEs

Credits