CVE Tools

CVE-2024-53259

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

CVE-2024-53259 affects Quic-go (CVSS 6.5, Medium).

No known exploitation. EPSS puts it in the 50th percentile. Fixed in 0.48.2.

Check it yourself

OpenVAS · 3 checks

e.g. OID 1.3.6.1.4.1.25623.1.0.154618

Run the check

Published Updated Sources: CVE.org, NVD, GitHub, BDU

What to do

Find your product and version, then upgrade to the build on the right.

  • Quic-goAffected: < 0.48.2Upgrade to: not statedStated by: CVE record
  • Go github.com/quic-go/quic-goAffected: < 0.48.2Upgrade to: 0.48.2Stated by: GitHub advisory
  • Red Hat Inc. Openshift Service MeshAffected: 2Upgrade to: not statedStated by: BDU
  • Red Hat Inc. Red Hat Advanced Cluster Management for KubernetesAffected: 2Upgrade to: not statedStated by: BDU
  • Red Hat Inc. Red Hat OpenShift Container PlatformAffected: 4Upgrade to: not statedStated by: BDU

Versions as the sources state them. 2 more products have version data. Full version matrix after sign-in

What it is

From the CVE record

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.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS50th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.6% chance of exploitation activity in the next 30 days, which ranks it in the 50th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

6 events over 570 days, from the signal feeds we watch.

  1. OpenVAS check added
  2. Patch availablepublished, weakness classified, att&ck mapped, record updated

Affected products

Technical detail

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Scored 6.5 by NVD.

How it is reached

  • Attack Vector AdjacentRequires access to the local network (e.g. same Wi-Fi, Bluetooth)
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality NoneNo confidentiality impact
  • Integrity NoneNo integrity impact
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Questions about CVE-2024-53259

Is CVE-2024-53259 being exploited?
No exploitation is confirmed and no public exploit is known. EPSS puts the chance of exploitation in the next 30 days at 0.6%.
Which versions are affected by CVE-2024-53259?
Quic-go: < 0.48.2. Github.com/quic-go/quic-go: < 0.48.2. Openshift Service Mesh: 2. 4 more products are listed in the record.
How do I fix or mitigate CVE-2024-53259?
Upgrade to 0.48.2 or later. The advisory is on github.com.

Last updated

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Quic-go, not every advisory.