Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

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

CVSS 3.1 6.5 MEDIUMEUVD CVSS 3.1 6.5 CVSS 3.1 · [email protected] · Secondary 6.5 MEDIUMCVSS_V3 CVSS_V4 Publisher rating MODERATEFixed by github.com/quic-go/quic-go 0.48.2osv · severity unknownFixed by github.com/quic-go/quic-go 0.48.2KEV status unknown

cve-program · CVE-2024-53259

Published

quic-go is an implementation of the QUIC protocol in Go. 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). The attacker needs to at least know the client's IP and port tuple to mount an attack. This vulnerability is fixed in 0.48.2.

Read the publisher's advisory

euvd · EUVD-2024-3494

Published

quic-go is an implementation of the QUIC protocol in Go. 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). The attacker needs to at least know the client's IP and port tuple to mount an attack. This vulnerability is fixed in 0.48.2.

Read the publisher's advisory

nvd · CVE-2024-53259

Published

quic-go is an implementation of the QUIC protocol in Go. 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). The attacker needs to at least know the client's IP and port tuple to mount an attack. This vulnerability is fixed in 0.48.2.

Read the publisher's advisory

osv · GHSA-px8v-pp82-rcvr

Published

### 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/

Read the publisher's advisory

osv · GO-2024-3302

Published

ICMP Packet Too Large Injection Attack on Linux in github.com/quic-go/quic-go

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2024-53259

Published

quic-go

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "quic-go",
                    "product": "quic-go",
                    "versions": [
                        {
                            "version": "< 0.48.2",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2024-3494

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Dec 2, 2024, 4:12:40 PM

dateUpdated: Dec 2, 2024, 7:28:08 PM

8 related source bulletins · separate from aliases

RHSA-2025:4810: Red Hat Security Advisory: RHSA: Submariner 0.18.5 - bug and security update

CVE-2024-45336 · CVE-2024-53259 · CVE-2025-22866 · CVE-2025-22868 · CVE-2025-30204

openSUSE-SU-2024:14567-1: govulncheck-vulndb-0.0.20241209T183251-1.1 on GA media

CVE-2024-10220 · CVE-2024-36620 · CVE-2024-36621 · CVE-2024-36623 · CVE-2024-37820 · CVE-2024-43784 · CVE-2024-45719 · CVE-2024-50948 · CVE-2024-52003 · CVE-2024-52529 · CVE-2024-52801 · CVE-2024-53259 · CVE-2024-53264 · CVE-2024-53858 · CVE-2024-53862 · CVE-2024-54131 · CVE-2024-54132 · CVE-2024-6156 · CVE-2024-6219 · CVE-2024-6538 · CVE-2024-8676

RHSA-2025:0385: Red Hat Security Advisory: VolSync 0.11.1 for RHEL 9

CVE-2024-45337 · CVE-2024-45338 · CVE-2024-53259

RHSA-2025:0386: Red Hat Security Advisory: VolSync 0.10.2 for RHEL 9

CVE-2024-45337 · CVE-2024-45338 · CVE-2024-53259

openSUSE-SU-2024:14544-1: teleport-17.0.3-1.1 on GA media

CVE-2024-53259

msrc_CVE-2024-53259: quic-go affected by an ICMP Packet Too Large Injection Attack on Linux

CVE-2024-53259

RHSA-2025:4250: Red Hat Security Advisory: RHSA: Submariner 0.19.4 - bug fix and enhancement update

CVE-2024-53259 · CVE-2025-22868 · CVE-2025-30204

RHSA-2024:10766: Red Hat Security Advisory: Red Hat Ansible Automation Platform 2.5 Product Security and Bug Fix Update

CVE-2024-52304 · CVE-2024-53259

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2024-53259

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Deferred

Weakness classifications: CWE-345

Original publisher date fields

published: 2024-12-02T17:15:12.767

lastModified: 2026-06-17T08:08:42.437

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-px8v-pp82-rcvr

Published

github.com/quic-go/quic-go

Go

SEMVER · introduced 0 → fixed 0.48.2

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GO-2024-3302

Published

github.com/quic-go/quic-go

Go

SEMVER · introduced 0 → fixed 0.48.2

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 13:53 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current