<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 03 Oct 2026 07:37:01 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-03135</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-03135</link>
      <description>bdu:2024-03135</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-03135</guid>
    </item>
    <item>
      <title>EUVD-2026-159781</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-159781</link>
      <description>EUVD-2026-159781</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-159781</guid>
    </item>
    <item>
      <title>fkie_cve-2024-22189</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-22189</link>
      <description>&lt;p&gt;quic-go is an implementation of the QUIC protocol in Go. Prior to version 0.42.0, an attacker can cause its peer to run out of memory sending a large number of `NEW_CONNECTION_ID` frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a `RETIRE_CONNECTION_ID` frame. The attacker can prevent the receiver from sending out (the vast majority of) these `RETIRE_CONNECTION_ID` frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer&amp;#39;s RTT estimate. Version 0.42.0 contains a patch for the issue. No known workarounds are available.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;quic-go is an implementation of the QUIC protocol in Go. Prior to version 0.42.0, an attacker can cause its peer to run out of memory sending a large number of `NEW_CONNECTION_ID` frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a `RETIRE_CONNECTION_ID` frame. The attacker can prevent the receiver from sending out (the vast majority of) these `RETIRE_CONNECTION_ID` frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer&amp;#39;s RTT estimate. Version 0.42.0 contains a patch for the issue. No known workarounds are available.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-22189</guid>
    </item>
    <item>
      <title>GHSA-c33x-xqrf-c478 — QUIC's Connection ID Mechanism vulnerable to Memory Exhaustion Attack</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-c33x-xqrf-c478</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/quic-go/quic-go&lt;/p&gt;
&lt;p&gt;An attacker can cause its peer to run out of memory by sending a large number of NEW_CONNECTION_ID frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a RETIRE_CONNECTION_ID frame. The attacker can prevent the receiver from sending out (the vast majority of) these RETIRE_CONNECTION_ID frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer&amp;#39;s RTT estimate.&lt;/p&gt;
&lt;p&gt;I published a more detailed description of the attack and its mitigation in this blog post: https://seemann.io/posts/2024-03-19-exploiting-quics-connection-id-management/.
I also presented this attack in the IETF QUIC working group session at IETF 119: https://youtu.be/JqXtYcZAtIA?si=nJ31QKLBSTRXY35U&amp;amp;t=3683&lt;/p&gt;
&lt;p&gt;There&amp;#39;s no way to mitigate this attack, please update quic-go to a version that contains the fix.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/quic-go/quic-go&lt;/p&gt;
&lt;p&gt;An attacker can cause its peer to run out of memory by sending a large number of NEW_CONNECTION_ID frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a RETIRE_CONNECTION_ID frame. The attacker can prevent the receiver from sending out (the vast majority of) these RETIRE_CONNECTION_ID frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer&amp;#39;s RTT estimate.&lt;/p&gt;
&lt;p&gt;I published a more detailed description of the attack and its mitigation in this blog post: https://seemann.io/posts/2024-03-19-exploiting-quics-connection-id-management/.
I also presented this attack in the IETF QUIC working group session at IETF 119: https://youtu.be/JqXtYcZAtIA?si=nJ31QKLBSTRXY35U&amp;amp;t=3683&lt;/p&gt;
&lt;p&gt;There&amp;#39;s no way to mitigate this attack, please update quic-go to a version that contains the fix.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-c33x-xqrf-c478</guid>
    </item>
    <item>
      <title>gsd-2024-22189</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-22189</link>
      <description>gsd-2024-22189</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-22189</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-22189 — QUIC's Connection ID Mechanism vulnerable to Memory Exhaustion Attack</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-22189</link>
      <description>msrc_CVE-2024-22189</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-22189</guid>
    </item>
    <item>
      <title>openSUSE-RU-2026:21160-1 — Recommended update for dnscrypt-proxy</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-ru-2026:21160-1</link>
      <description>&lt;p&gt;Recommended update for dnscrypt-proxy&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Recommended update for dnscrypt-proxy&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-ru-2026:21160-1</guid>
    </item>
    <item>
      <title>RHSA-2024:0041 — Red Hat Security Advisory: OpenShift Container Platform 4.16.0 bug fix and security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2024:0041</link>
      <description>&lt;p&gt;helm: shows secrets with --dry-run option in clear text opentelemetry: DoS vulnerability in otelhttp golang: net/http/cookiejar: incorrect forwarding of sensitive headers and cookies on HTTP redirect opentelemetry-go-contrib: DoS vulnerability in otelgrpc due to unbound cardinality metrics ssh: Prefix truncation attack on Binary Packet Protocol (BPP) go-git: Maliciously crafted Git server replies can lead to path traversal and RCE on go-git clients coredns: CD bit response is cached and served later quic-go: memory exhaustion attack against QUIC&amp;#39;s connection ID mechanism golang: crypto/x509: Verify panics on certificates with an unknown public key algorithm golang: net/mail: comments in display names are incorrectly handled golang: html/template: errors returned from MarshalJSON methods may break template escaping golang-protobuf: encoding/protojson, internal/encoding/json: infinite loop in protojson.Unmarshal when unmarshaling certain forms of invalid JSON cloudevents/sdk-go: usage of WithRoundTripper to create a Client leaks credentials jose: resource exhaustion jose-go: improper handling of highly compressed data follow-redirects: Possible credential leak webpack-dev-middleware: lack of URL validation may lead to file leak&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;helm: shows secrets with --dry-run option in clear text opentelemetry: DoS vulnerability in otelhttp golang: net/http/cookiejar: incorrect forwarding of sensitive headers and cookies on HTTP redirect opentelemetry-go-contrib: DoS vulnerability in otelgrpc due to unbound cardinality metrics ssh: Prefix truncation attack on Binary Packet Protocol (BPP) go-git: Maliciously crafted Git server replies can lead to path traversal and RCE on go-git clients coredns: CD bit response is cached and served later quic-go: memory exhaustion attack against QUIC&amp;#39;s connection ID mechanism golang: crypto/x509: Verify panics on certificates with an unknown public key algorithm golang: net/mail: comments in display names are incorrectly handled golang: html/template: errors returned from MarshalJSON methods may break template escaping golang-protobuf: encoding/protojson, internal/encoding/json: infinite loop in protojson.Unmarshal when unmarshaling certain forms of invalid JSON cloudevents/sdk-go: usage of WithRoundTripper to create a Client leaks credentials jose: resource exhaustion jose-go: improper handling of highly compressed data follow-redirects: Possible credential leak webpack-dev-middleware: lack of URL validation may lead to file leak&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2024:0041</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-22189</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-22189</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: golang-github-lucas-clemente-quic-go&lt;/p&gt;
&lt;p&gt;quic-go is an implementation of the QUIC protocol in Go. Prior to version 0.42.0, an attacker can cause its peer to run out of memory sending a large number of `NEW_CONNECTION_ID` frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a `RETIRE_CONNECTION_ID` frame. The attacker can prevent the receiver from sending out (the vast majority of) these `RETIRE_CONNECTION_ID` frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer&amp;#39;s RTT estimate. Version 0.42.0 contains a patch for the issue. No known workarounds are available.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: golang-github-lucas-clemente-quic-go&lt;/p&gt;
&lt;p&gt;quic-go is an implementation of the QUIC protocol in Go. Prior to version 0.42.0, an attacker can cause its peer to run out of memory sending a large number of `NEW_CONNECTION_ID` frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a `RETIRE_CONNECTION_ID` frame. The attacker can prevent the receiver from sending out (the vast majority of) these `RETIRE_CONNECTION_ID` frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer&amp;#39;s RTT estimate. Version 0.42.0 contains a patch for the issue. No known workarounds are available.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-22189</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1474 — Red Hat OpenShift Container Platform: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1474</link>
      <description>&lt;p&gt;Ein entfernter, anonymer oder lokaler Angreifer kann mehrere Schwachstellen in Red Hat OpenShift ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen, vertrauliche Informationen offenzulegen oder Daten zu manipulieren.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer oder lokaler Angreifer kann mehrere Schwachstellen in Red Hat OpenShift ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen, vertrauliche Informationen offenzulegen oder Daten zu manipulieren.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1474</guid>
    </item>
  </channel>
</rss>
