MediumGHSA-px8v-pp82-rcvrCVE-2024-53259GO-2024-3302

quic-go affected by an ICMP Packet Too Large Injection Attack on Linux

Published 2 Dec 2024 · Updated 10 Sept 2026

Is your project on an affected github.com/quic-go/quic-go?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<0.48.2
Fixed in
0.48.2
Update to the fixed version for your release line, for example:go get github.com/quic-go/quic-go@v0.48.2

Details

Impact

An off-path attacker can inject an ICMP Packet Too Large packet. Since affected quic-go versions used IP_PMTUDISC_DO, the kernel would then return a "message too large" error on sendmsg, i.e. when quic-go attempts to send a packet that exceeds the MTU claimed in that ICMP packet.

By setting this value to smaller than 1200 bytes (the minimum MTU for QUIC), the attacker can disrupt a QUIC connection. Crucially, this can be done after completion of the handshake, thereby circumventing any TCP fallback that might be implemented on the application layer (for example, many browsers fall back to HTTP over TCP if they're unable to establish a QUIC connection).

As far as I understand, the kernel tracks the MTU per 4-tuple, so the attacker needs to at least know the client's IP and port tuple to mount an attack (assuming that it knows the server's IP and port).

Patches

The fix is easy: Use IP_PMTUDISC_PROBE instead of IP_PMTUDISC_DO. This socket option only sets the DF bit, but disables the kernel's MTU tracking.

_Has the problem been patched? What versions should users upgrade to?_

Fixed in https://github.com/quic-go/quic-go/pull/4729 Released in https://github.com/quic-go/quic-go/releases/tag/v0.48.2

Workarounds

_Is there a way for users to fix or remediate the vulnerability without upgrading?_

Use iptables to drop ICMP Unreachable packets.

References

_Are there any links users can visit to find out more?_

This bug was discovered while doing research for my new IETF draft on IP fragmentation: https://datatracker.ietf.org/doc/draft-seemann-tsvwg-udp-fragmentation/

Is GHSA-px8v-pp82-rcvr in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/quic-go/quic-go, and gives you the command that fixes it.

More advisories for github.com/quic-go/quic-go

  • LowCVE-2026-40898HTTP/3 QPACK Trailer Expansion Memory Exhaustion in github.com/quic-go/quic-go · 7 Jul 2026
  • MediumCVE-2026-40898quic-go: HTTP/3 QPACK Trailer Expansion Memory Exhaustion · 3 Jun 2026
  • LowCVE-2025-64702HTTP/3 QPACK Header Expansion DoS in github.com/quic-go/quic-go · 15 Dec 2025
  • MediumCVE-2025-64702quic-go HTTP/3 QPACK Header Expansion DoS · 11 Dec 2025
  • LowCVE-2025-59530Panic occurs when queuing undecryptable packets after handshake completion in github.com/quic-go/quic-go · 5 Nov 2025
  • HighCVE-2025-59530quic-go: Panic occurs when queuing undecryptable packets after handshake completion · 10 Oct 2025
All 15 advisories for github.com/quic-go/quic-go

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.