Advisory

RUSTSEC-2026-0338

Also known as: GHSA-465w-v9q3-7j98

Summary

Remote peer can panic quinn-proto with zero-length STREAM frames during unordered reads

Details

When a stream is read in unordered mode (for example through RecvStream::read(false) in
quinn-proto or read_unordered in quinn), quinn-proto proactively deduplicates received data
by recording received ranges in a RangeSet through its replace method. When an incoming
STREAM frame carried an empty payload, the Drop implementation of the iterator returned by
replace inserted an empty range into the set, violating the invariant that stored ranges are
non-empty. Subsequent frames overlapping that region then caused a panic while processing the
stream.

A remote peer can trigger this with five small STREAM frames (two of them zero-length) once the
application has put the stream in unordered-read mode. The default ordered read path is not
affected.

The flaw was corrected in 0.11.18 by ignoring empty ranges in RangeSet::replace.

Thanks to Otto Hermann (@ojhermann) for reporting this issue.

Severity

Not rated by the source.

Dates

Published
2026-09-14 12:00 UTC
Modified
2026-10-12 18:15 UTC

Affected packages and fixes

quinn-proto

crates.io · All systems

Affected

  • introduced 0.7.0, fixed 0.11.18 (semver)

Fixed versions

0.11.18

Fix

  • Fixed version 0.11.18
    cargo update -p quinn-proto --precise 0.11.18

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: RustSec Advisory Database · CC0-1.0

Sources & licences