<?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>Tue, 06 Oct 2026 20:12:27 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-06667</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-06667</link>
      <description>bdu:2024-06667</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-06667</guid>
    </item>
    <item>
      <title>BIT-vault-2024-6468 — Vault Vulnerable to Denial of Service When Setting a Proxy Protocol Behavior</title>
      <link>https://cve.radiocsirt.org/vuln/bit-vault-2024-6468</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: vault&lt;/p&gt;
&lt;p&gt;Vault and Vault Enterprise did not properly handle requests originating from unauthorized IP addresses when the TCP listener option, proxy_protocol_behavior, was set to deny_unauthorized. When receiving a request from a source IP address that was not listed in proxy_protocol_authorized_addrs, the Vault API server would shut down and no longer respond to any HTTP requests, potentially resulting in denial of service.&lt;/p&gt;
&lt;p&gt;While this bug also affected versions of Vault up to 1.17.1 and 1.16.5, a separate regression in those release series did not allow Vault operators to configure the deny_unauthorized option, thus not allowing the conditions for the denial of service to occur.&lt;/p&gt;
&lt;p&gt;Fixed in Vault and Vault Enterprise 1.17.2, 1.16.6, and 1.15.12.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: vault&lt;/p&gt;
&lt;p&gt;Vault and Vault Enterprise did not properly handle requests originating from unauthorized IP addresses when the TCP listener option, proxy_protocol_behavior, was set to deny_unauthorized. When receiving a request from a source IP address that was not listed in proxy_protocol_authorized_addrs, the Vault API server would shut down and no longer respond to any HTTP requests, potentially resulting in denial of service.&lt;/p&gt;
&lt;p&gt;While this bug also affected versions of Vault up to 1.17.1 and 1.16.5, a separate regression in those release series did not allow Vault operators to configure the deny_unauthorized option, thus not allowing the conditions for the denial of service to occur.&lt;/p&gt;
&lt;p&gt;Fixed in Vault and Vault Enterprise 1.17.2, 1.16.6, and 1.15.12.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bit-vault-2024-6468</guid>
    </item>
    <item>
      <title>EUVD-2026-3384</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-3384</link>
      <description>EUVD-2026-3384</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-3384</guid>
    </item>
    <item>
      <title>fkie_cve-2024-6468</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-6468</link>
      <description>&lt;p&gt;Vault and Vault Enterprise did not properly handle requests originating from unauthorized IP addresses when the TCP listener option, proxy_protocol_behavior, was set to deny_unauthorized. When receiving a request from a source IP address that was not listed in proxy_protocol_authorized_addrs, the Vault API server would shut down and no longer respond to any HTTP requests, potentially resulting in denial of service.&lt;/p&gt;
&lt;p&gt;While this bug also affected versions of Vault up to 1.17.1 and 1.16.5, a separate regression in those release series did not allow Vault operators to configure the deny_unauthorized option, thus not allowing the conditions for the denial of service to occur.&lt;/p&gt;
&lt;p&gt;Fixed in Vault and Vault Enterprise 1.17.2, 1.16.6, and 1.15.12.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Vault and Vault Enterprise did not properly handle requests originating from unauthorized IP addresses when the TCP listener option, proxy_protocol_behavior, was set to deny_unauthorized. When receiving a request from a source IP address that was not listed in proxy_protocol_authorized_addrs, the Vault API server would shut down and no longer respond to any HTTP requests, potentially resulting in denial of service.&lt;/p&gt;
&lt;p&gt;While this bug also affected versions of Vault up to 1.17.1 and 1.16.5, a separate regression in those release series did not allow Vault operators to configure the deny_unauthorized option, thus not allowing the conditions for the denial of service to occur.&lt;/p&gt;
&lt;p&gt;Fixed in Vault and Vault Enterprise 1.17.2, 1.16.6, and 1.15.12.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-6468</guid>
    </item>
    <item>
      <title>GHSA-2qmw-pvf7-4mw6 — Hashicorp Vault vulnerable to Improper Check or Handling of Exceptional Conditions</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2qmw-pvf7-4mw6</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/hashicorp/vault&lt;/p&gt;
&lt;p&gt;Vault and Vault Enterprise did not properly handle requests originating from unauthorized IP addresses when the TCP listener option, proxy_protocol_behavior, was set to deny_unauthorized. When receiving a request from a source IP address that was not listed in proxy_protocol_authorized_addrs, the Vault API server would shut down and no longer respond to any HTTP requests, potentially resulting in denial of service.&lt;/p&gt;
&lt;p&gt;While this bug also affected versions of Vault up to 1.17.1 and 1.16.5, a separate regression in those release series did not allow Vault operators to configure the deny_unauthorized option, thus not allowing the conditions for the denial of service to occur.&lt;/p&gt;
&lt;p&gt;Fixed in Vault and Vault Enterprise 1.17.2, 1.16.6, and 1.15.12&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/hashicorp/vault&lt;/p&gt;
&lt;p&gt;Vault and Vault Enterprise did not properly handle requests originating from unauthorized IP addresses when the TCP listener option, proxy_protocol_behavior, was set to deny_unauthorized. When receiving a request from a source IP address that was not listed in proxy_protocol_authorized_addrs, the Vault API server would shut down and no longer respond to any HTTP requests, potentially resulting in denial of service.&lt;/p&gt;
&lt;p&gt;While this bug also affected versions of Vault up to 1.17.1 and 1.16.5, a separate regression in those release series did not allow Vault operators to configure the deny_unauthorized option, thus not allowing the conditions for the denial of service to occur.&lt;/p&gt;
&lt;p&gt;Fixed in Vault and Vault Enterprise 1.17.2, 1.16.6, and 1.15.12&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2qmw-pvf7-4mw6</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1603 — Hashicorp Vault: Schwachstelle ermöglicht Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1603</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Hashicorp Vault ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Hashicorp Vault ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1603</guid>
    </item>
  </channel>
</rss>
