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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.0 · CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2024-53259: 0.60% estimated exploitation activity in the next 30 days; percentile 48.93 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact An off-path attacker can inject an ICMP Packet Too Large packet. Since affected quic-go versions used IPPMTUDISCDO, 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 IPPMTUDISCPROBE instead of IPPMTUDISCDO. This socket option only sets the DF bit, but disables the…

Published by the source

2 Dec 2024, 17:28 UTC

Last modified by the source

4 Dec 2024, 22:16 UTC

Source last checked

26 Oct 2026, 15:08 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-px8v-pp82-rcvr

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-53259

Advisory: quic-go affected by an ICMP Packet Too Large Injection Attack on Linux
IDs: CVE-2024-53259, GHSA-px8v-pp82-rcvr
Record: https://patchnext.com/advisories/cve-2024-53259 (revision 1, source checked 26 Oct 2026, 15:08 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/quic-go/quic-go 0.48.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/quic-go/quic-go: affected < 0.48.2; fixed in 0.48.2

## Suggested inspection (read-only)
- Go github.com/quic-go/quic-go: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/quic-go/quic-go.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-px8v-pp82-rcvr (GitHub-reviewed advisory GHSA-px8v-pp82-rcvr lists affected ranges: Go github.com/quic-go/quic-go >=0 <0.48.2)

Commands are suggestions: review each one before running it.