<?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 15:02:23 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-03289</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-03289</link>
      <description>bdu:2024-03289</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-03289</guid>
    </item>
    <item>
      <title>BIT-envoy-2024-32475 — Envoy RELEASE_ASSERT using auto_sni with :authority header &gt; 255 bytes</title>
      <link>https://cve.radiocsirt.org/vuln/bit-envoy-2024-32475</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: envoy&lt;/p&gt;
&lt;p&gt;Envoy is a cloud-native, open source edge and service proxy. When an upstream TLS cluster is used with `auto_sni` enabled, a request containing a `host`/`:authority` header longer than 255 characters triggers an abnormal termination of Envoy process. Envoy does not gracefully handle an error when setting SNI for outbound TLS connection. The error can occur when Envoy attempts to use the `host`/`:authority` header value longer than 255 characters as SNI for outbound TLS connection. SNI length is limited to 255 characters per the standard. Envoy always expects this operation to succeed and abnormally aborts the process when it fails. This vulnerability is fixed in 1.30.1, 1.29.4, 1.28.3, and 1.27.5.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: envoy&lt;/p&gt;
&lt;p&gt;Envoy is a cloud-native, open source edge and service proxy. When an upstream TLS cluster is used with `auto_sni` enabled, a request containing a `host`/`:authority` header longer than 255 characters triggers an abnormal termination of Envoy process. Envoy does not gracefully handle an error when setting SNI for outbound TLS connection. The error can occur when Envoy attempts to use the `host`/`:authority` header value longer than 255 characters as SNI for outbound TLS connection. SNI length is limited to 255 characters per the standard. Envoy always expects this operation to succeed and abnormally aborts the process when it fails. This vulnerability is fixed in 1.30.1, 1.29.4, 1.28.3, and 1.27.5.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bit-envoy-2024-32475</guid>
    </item>
    <item>
      <title>EUVD-2026-5142</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-5142</link>
      <description>EUVD-2026-5142</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-5142</guid>
    </item>
    <item>
      <title>fkie_cve-2024-32475</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-32475</link>
      <description>&lt;p&gt;Envoy is a cloud-native, open source edge and service proxy. When an upstream TLS cluster is used with `auto_sni` enabled, a request containing a `host`/`:authority` header longer than 255 characters triggers an abnormal termination of Envoy process. Envoy does not gracefully handle an error when setting SNI for outbound TLS connection. The error can occur when Envoy attempts to use the `host`/`:authority` header value longer than 255 characters as SNI for outbound TLS connection. SNI length is limited to 255 characters per the standard. Envoy always expects this operation to succeed and abnormally aborts the process when it fails. This vulnerability is fixed in 1.30.1, 1.29.4, 1.28.3, and 1.27.5.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Envoy is a cloud-native, open source edge and service proxy. When an upstream TLS cluster is used with `auto_sni` enabled, a request containing a `host`/`:authority` header longer than 255 characters triggers an abnormal termination of Envoy process. Envoy does not gracefully handle an error when setting SNI for outbound TLS connection. The error can occur when Envoy attempts to use the `host`/`:authority` header value longer than 255 characters as SNI for outbound TLS connection. SNI length is limited to 255 characters per the standard. Envoy always expects this operation to succeed and abnormally aborts the process when it fails. This vulnerability is fixed in 1.30.1, 1.29.4, 1.28.3, and 1.27.5.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-32475</guid>
    </item>
    <item>
      <title>gsd-2024-32475</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-32475</link>
      <description>gsd-2024-32475</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-32475</guid>
    </item>
    <item>
      <title>RHSA-2024:7724 — Red Hat Security Advisory: Red Hat OpenShift Service Mesh Containers for 2.4.11</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2024:7724</link>
      <description>&lt;p&gt;envoy: abnormal termination when using auto_sni with authority header longer than 255 characters envoy: Brotli decompressor infinite loop webpack: DOM Clobbering vulnerability in AutoPublicPathRuntimeModule send: Code Execution Vulnerability in Send Library serve-static: Improper Sanitization in serve-static&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;envoy: abnormal termination when using auto_sni with authority header longer than 255 characters envoy: Brotli decompressor infinite loop webpack: DOM Clobbering vulnerability in AutoPublicPathRuntimeModule send: Code Execution Vulnerability in Send Library serve-static: Improper Sanitization in serve-static&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2024:7724</guid>
    </item>
  </channel>
</rss>
