<?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 10:59:45 +0000</lastBuildDate>
    <item>
      <title>cnvd-2022-09804</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2022-09804</link>
      <description>cnvd-2022-09804</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2022-09804</guid>
    </item>
    <item>
      <title>EUVD-2026-33091</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-33091</link>
      <description>EUVD-2026-33091</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-33091</guid>
    </item>
    <item>
      <title>fkie_cve-2021-44878</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-44878</link>
      <description>&lt;p&gt;If an OpenID Connect provider supports the &amp;#34;none&amp;#34; algorithm (i.e., tokens with no signature), pac4j v5.3.0 (and prior) does not refuse it without an explicit configuration on its side or for the &amp;#34;idtoken&amp;#34; response type which is not secure and violates the OpenID Core Specification. The &amp;#34;none&amp;#34; algorithm does not require any signature verification when validating the ID tokens, which allows the attacker to bypass the token validation by injecting a malformed ID token using &amp;#34;none&amp;#34; as the value of &amp;#34;alg&amp;#34; key in the header with an empty signature value.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;If an OpenID Connect provider supports the &amp;#34;none&amp;#34; algorithm (i.e., tokens with no signature), pac4j v5.3.0 (and prior) does not refuse it without an explicit configuration on its side or for the &amp;#34;idtoken&amp;#34; response type which is not secure and violates the OpenID Core Specification. The &amp;#34;none&amp;#34; algorithm does not require any signature verification when validating the ID tokens, which allows the attacker to bypass the token validation by injecting a malformed ID token using &amp;#34;none&amp;#34; as the value of &amp;#34;alg&amp;#34; key in the header with an empty signature value.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-44878</guid>
    </item>
    <item>
      <title>GHSA-xhw6-hjc9-679m — Pac4j token validation bypass if OpenID Connect provider supports none algorithm</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-xhw6-hjc9-679m</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.pac4j:pac4j-oidc&lt;/p&gt;
&lt;p&gt;If an OpenID Connect provider supports the “none” algorithm (i.e., tokens with no signature), pac4j v5.3.0 (and prior) does not refuse it without an explicit configuration on its side or for the “idtoken” response type which is not secure and violates the OpenID Core Specification. The &amp;#34;none&amp;#34; algorithm does not require any signature verification when validating the ID tokens, which allows the attacker to bypass the token validation by injecting a malformed ID token using &amp;#34;none&amp;#34; as the value of &amp;#34;alg&amp;#34; key in the header with an empty signature value.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.pac4j:pac4j-oidc&lt;/p&gt;
&lt;p&gt;If an OpenID Connect provider supports the “none” algorithm (i.e., tokens with no signature), pac4j v5.3.0 (and prior) does not refuse it without an explicit configuration on its side or for the “idtoken” response type which is not secure and violates the OpenID Core Specification. The &amp;#34;none&amp;#34; algorithm does not require any signature verification when validating the ID tokens, which allows the attacker to bypass the token validation by injecting a malformed ID token using &amp;#34;none&amp;#34; as the value of &amp;#34;alg&amp;#34; key in the header with an empty signature value.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-xhw6-hjc9-679m</guid>
    </item>
    <item>
      <title>gsd-2021-44878</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-44878</link>
      <description>gsd-2021-44878</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-44878</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-0794 — Dell ECS: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0794</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Dell ECS ausnutzen, um seine Privilegien zu erweitern, beliebigen Programmcode mit Administratorrechten auszuführen, Informationen offenzulegen, Dateien zu manipulieren, einen Cross-Site-Scripting-Angriff durchzuführen, Sicherheitsvorkehrungen zu umgehen oder einen Denial of Service Zustand herbeizuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Dell ECS ausnutzen, um seine Privilegien zu erweitern, beliebigen Programmcode mit Administratorrechten auszuführen, Informationen offenzulegen, Dateien zu manipulieren, einen Cross-Site-Scripting-Angriff durchzuführen, Sicherheitsvorkehrungen zu umgehen oder einen Denial of Service Zustand herbeizuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0794</guid>
    </item>
  </channel>
</rss>
