Advisory

RUSTSEC-2026-0340

Also known as: GHSA-3g6h-r5qx-f6hq

Summary

Peer minimum ACK delay can panic quinn-proto when ACK_FREQUENCY transmission is enabled

Details

When sending ACK_FREQUENCY frames is enabled through
TransportConfig::ack_frequency_config(Some(..)), the peer's transport parameters could cause
AckFrequencyState::candidate_max_ack_delay to call Duration::clamp with a minimum greater
than its maximum, which panics.

For example, a peer advertising a min_ack_delay of 100,000 microseconds and a max_ack_delay
of 100 milliseconds passes transport parameter validation. At a 5 ms RTT, the lower bound of the
clamp becomes 100 ms while the upper bound is 25 ms, violating the precondition of clamp and
panicking while driving the connection. Both automatically derived and explicitly configured
maximum ACK delays use this calculation.

Sending ACK_FREQUENCY frames is disabled by default, so only endpoints that opt in are affected.

The flaw was corrected in 0.11.18 by computing the delay with explicit minimum and maximum bounds
instead of clamp.

Thanks to @zerox80 for reporting this issue.

Severity

High Basis: CVSS v3 score 7.5, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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.11.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