Advisory

GHSA-c33x-xqrf-c478

Also known as: CVE-2024-22189, GO-2024-2682

Summary

QUIC's Connection ID Mechanism vulnerable to Memory Exhaustion Attack

Details

An attacker can cause its peer to run out of memory by sending a large number of NEW_CONNECTION_ID frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a RETIRE_CONNECTION_ID frame. The attacker can prevent the receiver from sending out (the vast majority of) these RETIRE_CONNECTION_ID frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate.

I published a more detailed description of the attack and its mitigation in this blog post: https://seemann.io/posts/2024-03-19-exploiting-quics-connection-id-management/.
I also presented this attack in the IETF QUIC working group session at IETF 119: https://youtu.be/JqXtYcZAtIA?si=nJ31QKLBSTRXY35U&t=3683

There's no way to mitigate this attack, please update quic-go to a version that contains the fix.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2024-04-02 14:16 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

github.com/quic-go/quic-go

Go · All systems

Affected

  • introduced 0, fixed 0.42.0 (semver)

Fixed versions

0.42.0

Fix

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: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences