Skip to content

Subtraction underflow when parsing Retry packets

Moderate
martinthomson published GHSA-hvhj-4r52-8568 Apr 17, 2024

Package

cargo neqo-transport (Rust)

Affected versions

<=0.7.4

Patched versions

0.7.5

Description

Impact

Experimenting with cargo fuzz in #1764 immediately revealed a possible subtraction underflow in this line

let token = Self::opt(decoder.decode(decoder.remaining() - expansion))?;

when decoder.remaining(), i.e., the leftover bytes in the incoming packet, is less than expansion. One input that triggers this crash is [179, 255, 0, 0, 32, 0, 0], but there are many others.

A misbehaving server can use this as a packet-of-death to crash the neqo stack (and possibly Fx?) by sending a malformed Retry packet in response to a QUIC Client Initial (for example).

Patches

A fix to the bug was merged in b3cf65f

Workarounds

None.

References

https://bugzilla.mozilla.org/show_bug.cgi?id=1886929

Severity

Moderate

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
Low

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:L

CVE ID

No known CVE

Weaknesses

No CWEs