<?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>Sun, 18 Oct 2026 02:36:50 +0000</lastBuildDate>
    <item>
      <title>certfr-2024-avi-0390 — Une vulnérabilité a été découverte dans Strongswan. Elle permet à un
attaquant de provoquer un contournement de la poli…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0390</link>
      <description>certfr-2024-avi-0390</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0390</guid>
    </item>
    <item>
      <title>EUVD-2026-216112</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-216112</link>
      <description>EUVD-2026-216112</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-216112</guid>
    </item>
    <item>
      <title>fkie_cve-2022-4967</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-4967</link>
      <description>&lt;p&gt;strongSwan versions 5.9.2 through 5.9.5 are affected by authorization bypass through improper validation of certificate with host mismatch (CWE-297). When certificates are used to authenticate clients in TLS-based EAP methods, the IKE or EAP identity supplied by a client is not enforced to be contained in the client&amp;#39;s certificate. So clients can authenticate with any trusted certificate and claim an arbitrary IKE/EAP identity as their own. This is problematic if the identity is used to make policy decisions. A fix was released in strongSwan version 5.9.6 in August 2022 (e4b4aabc4996fc61c37deab7858d07bc4d220136).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;strongSwan versions 5.9.2 through 5.9.5 are affected by authorization bypass through improper validation of certificate with host mismatch (CWE-297). When certificates are used to authenticate clients in TLS-based EAP methods, the IKE or EAP identity supplied by a client is not enforced to be contained in the client&amp;#39;s certificate. So clients can authenticate with any trusted certificate and claim an arbitrary IKE/EAP identity as their own. This is problematic if the identity is used to make policy decisions. A fix was released in strongSwan version 5.9.6 in August 2022 (e4b4aabc4996fc61c37deab7858d07bc4d220136).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-4967</guid>
    </item>
    <item>
      <title>GHSA-2hrc-c28p-9f59</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2hrc-c28p-9f59</link>
      <description>&lt;p&gt;strongSwan versions 5.9.2 through 5.9.5 are affected by authorization bypass through improper validation of certificate with host mismatch (CWE-297). When certificates are used to authenticate clients in TLS-based EAP methods, the IKE or EAP identity supplied by a client is not enforced to be contained in the client&amp;#39;s certificate. So clients can authenticate with any trusted certificate and claim an arbitrary IKE/EAP identity as their own. This is problematic if the identity is used to make policy decisions. A fix was released in strongSwan version 5.9.6 in August 2022 (e4b4aabc4996fc61c37deab7858d07bc4d220136).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;strongSwan versions 5.9.2 through 5.9.5 are affected by authorization bypass through improper validation of certificate with host mismatch (CWE-297). When certificates are used to authenticate clients in TLS-based EAP methods, the IKE or EAP identity supplied by a client is not enforced to be contained in the client&amp;#39;s certificate. So clients can authenticate with any trusted certificate and claim an arbitrary IKE/EAP identity as their own. This is problematic if the identity is used to make policy decisions. A fix was released in strongSwan version 5.9.6 in August 2022 (e4b4aabc4996fc61c37deab7858d07bc4d220136).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2hrc-c28p-9f59</guid>
    </item>
    <item>
      <title>gsd-2022-4967</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-4967</link>
      <description>gsd-2022-4967</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-4967</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-4967</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-4967</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: strongswan&lt;/p&gt;
&lt;p&gt;strongSwan versions 5.9.2 through 5.9.5 are affected by authorization bypass through improper validation of certificate with host mismatch (CWE-297). When certificates are used to authenticate clients in TLS-based EAP methods, the IKE or EAP identity supplied by a client is not enforced to be contained in the client&amp;#39;s certificate. So clients can authenticate with any trusted certificate and claim an arbitrary IKE/EAP identity as their own. This is problematic if the identity is used to make policy decisions. A fix was released in strongSwan version 5.9.6 in August 2022 (e4b4aabc4996fc61c37deab7858d07bc4d220136).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: strongswan&lt;/p&gt;
&lt;p&gt;strongSwan versions 5.9.2 through 5.9.5 are affected by authorization bypass through improper validation of certificate with host mismatch (CWE-297). When certificates are used to authenticate clients in TLS-based EAP methods, the IKE or EAP identity supplied by a client is not enforced to be contained in the client&amp;#39;s certificate. So clients can authenticate with any trusted certificate and claim an arbitrary IKE/EAP identity as their own. This is problematic if the identity is used to make policy decisions. A fix was released in strongSwan version 5.9.6 in August 2022 (e4b4aabc4996fc61c37deab7858d07bc4d220136).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-4967</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1138 — strongSwan: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1138</link>
      <description>&lt;p&gt;Ein entfernter, authentifizierter Angreifer kann eine Schwachstelle in strongSwan ausnutzen, um Sicherheitsvorkehrungen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, authentifizierter Angreifer kann eine Schwachstelle in strongSwan ausnutzen, um Sicherheitsvorkehrungen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1138</guid>
    </item>
  </channel>
</rss>
