https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 22:10:44 +0000 https://cve.radiocsirt.org/vuln/bdu:2024-10806 bdu:2024-10806 https://cve.radiocsirt.org/vuln/bdu:2024-10806 https://cve.radiocsirt.org/vuln/certfr-2024-avi-1092 certfr-2024-avi-1092 https://cve.radiocsirt.org/vuln/certfr-2024-avi-1092 https://cve.radiocsirt.org/vuln/cleanstart-2026-bb24925 <p><strong>Affected:</strong> CleanStart: kubernetes-dns-node-cache</p> <p>CVE-2024-53259 affects multiple packages. This issue is resolved in later releases. See references for individual vulnerability details.</p> <p><strong>Affected:</strong> CleanStart: kubernetes-dns-node-cache</p> <p>CVE-2024-53259 affects multiple packages. This issue is resolved in later releases. See references for individual vulnerability details.</p> https://cve.radiocsirt.org/vuln/cleanstart-2026-bb24925 https://cve.radiocsirt.org/vuln/euvd-2026-205363 EUVD-2026-205363 https://cve.radiocsirt.org/vuln/euvd-2026-205363 https://cve.radiocsirt.org/vuln/fkie_cve-2024-53259 <p>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 &#34;message too large&#34; 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&#39;re unable to establish a QUIC connection). The attacker needs to at least know the client&#39;s IP and port tuple to mount an attack. This vulnerability is fixed in 0.48.2.</p> <p>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 &#34;message too large&#34; 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&#39;re unable to establish a QUIC connection). The attacker needs to at least know the client&#39;s IP and port tuple to mount an attack. This vulnerability is fixed in 0.48.2.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-53259 https://cve.radiocsirt.org/vuln/ghsa-px8v-pp82-rcvr <p><strong>Affected:</strong> Go: github.com/quic-go/quic-go</p> <p>### 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 &#34;message too large&#34; error on `sendmsg`, i.e. when quic-go attempts to send a packet that exceeds the MTU claimed in that ICMP packet.</p> <p>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&#39;re unable to establish a QUIC connection).</p> <p>As far as I understand, the kernel tracks the MTU per 4-tuple, so the attacker needs to at least know the client&#39;s IP and port tuple to mount an attack (assuming that it knows the server&#39;s IP and port).</p> <p>### Patches</p> <p>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&#39;s MTU tracking.</p> <p>_Has the problem been patched? What versions should users upgrade to?_</p> <p>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</p> <p>### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_</p> <p>Use iptables to drop ICMP Unreachable packets.</p> <p>### References</p> <p>_Are there any links users can visit to find out more?_</p> <p>This bug was discovered while doing…</p> <p><strong>Affected:</strong> Go: github.com/quic-go/quic-go</p> <p>### 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 &#34;message too large&#34; error on `sendmsg`, i.e. when quic-go attempts to send a packet that exceeds the MTU claimed in that ICMP packet.</p> <p>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&#39;re unable to establish a QUIC connection).</p> <p>As far as I understand, the kernel tracks the MTU per 4-tuple, so the attacker needs to at least know the client&#39;s IP and port tuple to mount an attack (assuming that it knows the server&#39;s IP and port).</p> <p>### Patches</p> <p>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&#39;s MTU tracking.</p> <p>_Has the problem been patched? What versions should users upgrade to?_</p> <p>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</p> <p>### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_</p> <p>Use iptables to drop ICMP Unreachable packets.</p> <p>### References</p> <p>_Are there any links users can visit to find out more?_</p> <p>This bug was discovered while doing…</p> https://cve.radiocsirt.org/vuln/ghsa-px8v-pp82-rcvr https://cve.radiocsirt.org/vuln/msrc_cve-2024-53259 msrc_CVE-2024-53259 https://cve.radiocsirt.org/vuln/msrc_cve-2024-53259 https://cve.radiocsirt.org/vuln/opensuse-su-2024:14544-1 <p>teleport-17.0.3-1.1 on GA media</p> <p>teleport-17.0.3-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:14544-1 https://cve.radiocsirt.org/vuln/rhsa-2024:10766 <p>aiohttp: aiohttp vulnerable to request smuggling due to incorrect parsing of chunk extensions quic-go: quic-go affected by an ICMP Packet Too Large Injection Attack on Linux</p> <p>aiohttp: aiohttp vulnerable to request smuggling due to incorrect parsing of chunk extensions quic-go: quic-go affected by an ICMP Packet Too Large Injection Attack on Linux</p> https://cve.radiocsirt.org/vuln/rhsa-2024:10766 https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-53259 <p><strong>Affected:</strong> Ubuntu:22.04:LTS: golang-github-lucas-clemente-quic-go, Ubuntu:24.04:LTS: golang-github-lucas-clemente-quic-go, Ubuntu:25.10: golang-github-lucas-clemente-quic-go, Ubuntu:26.04:LTS: golang-github-lucas-clemente-quic-go</p> <p>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 &#34;message too large&#34; 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&#39;re unable to establish a QUIC connection). The attacker needs to at least know the client&#39;s IP and port tuple to mount an attack. This vulnerability is fixed in 0.48.2.</p> <p><strong>Affected:</strong> Ubuntu:22.04:LTS: golang-github-lucas-clemente-quic-go, Ubuntu:24.04:LTS: golang-github-lucas-clemente-quic-go, Ubuntu:25.10: golang-github-lucas-clemente-quic-go, Ubuntu:26.04:LTS: golang-github-lucas-clemente-quic-go</p> <p>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 &#34;message too large&#34; 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&#39;re unable to establish a QUIC connection). The attacker needs to at least know the client&#39;s IP and port tuple to mount an attack. This vulnerability is fixed in 0.48.2.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-53259