quinn-proto
Affected
- introduced
0.11.0, fixed0.11.18(semver)
Fixed versions
0.11.18
Fix
- Fixed version
0.11.18cargo update -p quinn-proto --precise 0.11.18
Advisory
Also known as: GHSA-3g6h-r5qx-f6hq
Peer minimum ACK delay can panic quinn-proto when ACK_FREQUENCY transmission is enabled
When sending ACK_FREQUENCY frames is enabled throughTransportConfig::ack_frequency_config(Some(..)), the peer's transport parameters could causeAckFrequencyState::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.
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
0.11.0, fixed 0.11.18 (semver)0.11.18
0.11.18cargo update -p quinn-proto --precise 0.11.18Fix 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
Source: RustSec Advisory Database · CC0-1.0