quic-go is an implementation of the QUIC protocol in Go. Prior to version 0.42.0, an attacker can cause its peer to run out of memory 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. Version 0.42.0 contains a patch for the issue. No known workarounds are available. https://github.com/quic-go/quic-go/commit/4a99b816ae3ab03ae5449d15aac45147c85ed47a https://github.com/quic-go/quic-go/security/advisories/GHSA-c33x-xqrf-c478 https://seemann.io/posts/2024-03-19-exploiting-quics-connection-id-management https://www.youtube.com/watch?v=JqXtYcZAtIA&t=3683s
Created caddy tracking bugs for this issue: Affects: epel-8 [bug 2273515] Affects: epel-all [bug 2273514] Affects: fedora-38 [bug 2273516] Affects: fedora-39 [bug 2273517]
Created dnscrypt-proxy tracking bugs for this issue: Affects: fedora-39 [bug 2275236] Created golang-github-quic tracking bugs for this issue: Affects: fedora-39 [bug 2275237] Created receptor tracking bugs for this issue: Affects: fedora-all [bug 2275234] Created syncthing tracking bugs for this issue: Affects: epel-8 [bug 2275233] Affects: fedora-38 [bug 2275235]
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.16 Via RHSA-2024:0041 https://access.redhat.com/errata/RHSA-2024:0041
This issue has been addressed in the following products: Red Hat OpenShift Service Mesh 2.6 for RHEL 8 Red Hat OpenShift Service Mesh 2.6 for RHEL 9 Via RHSA-2024:5094 https://access.redhat.com/errata/RHSA-2024:5094