GitHub Advisoryadvisory · Go

GHSA-c33x-xqrf-c478 QUIC's Connection ID Mechanism vulnerable to Memory Exhaustion Attack

HIGH Published 2024-04-02 Modified 2024-04-05 Official page ↗
Aliases
CVE-2024-22189
Ecosystem
Go
Packages
github.com/quic-go/quic-go
Severity
High
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weaknesses
CWE-400, CWE-770
Reviewed
2024-04-02

Affected packages

• Go github.com/quic-go/quic-go: < 0.42.0 → fixed in 0.42.0

Description

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.

Related

Alias · CVE (1)

  • CVE-2024-22189 quic-go is an implementation of the QUIC protocol in Go. vulnerability

Weakness · CWE (2)

  • CWE-400 Uncontrolled Resource Consumption weakness
  • CWE-770 Allocation of Resources Without Limits or Throttling weakness

References