<?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 23:19:05 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-64099 — OpenAM allows use of arbitrary OIDC requested claims values in id_token and user_info</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-64099</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; OpenIdentityPlatform OpenAM&lt;/p&gt;
&lt;p&gt;Open Access Management (OpenAM) is an access management solution. In versions prior to 16.0.0, if the &amp;#34;claims_parameter_supported&amp;#34; parameter is activated, it is possible, thanks to the &amp;#34;oidc-claims-extension.groovy&amp;#34; script, to inject the value of one&amp;#39;s choice into a claim contained in the id_token or in the user_info. In the request of an authorize function, a claims parameter containing a JSON file can be injected. This JSON file allows attackers to customize the claims returned by the &amp;#34;id_token&amp;#34; and &amp;#34;user_info&amp;#34; files. This allows for a very wide range of vulnerabilities depending on how clients use claims. For example, if some clients rely on an email field to identify a user, an attacker can choose the email address they want, and therefore assume any identity they choose. Version 16.0.0 fixes the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; OpenIdentityPlatform OpenAM&lt;/p&gt;
&lt;p&gt;Open Access Management (OpenAM) is an access management solution. In versions prior to 16.0.0, if the &amp;#34;claims_parameter_supported&amp;#34; parameter is activated, it is possible, thanks to the &amp;#34;oidc-claims-extension.groovy&amp;#34; script, to inject the value of one&amp;#39;s choice into a claim contained in the id_token or in the user_info. In the request of an authorize function, a claims parameter containing a JSON file can be injected. This JSON file allows attackers to customize the claims returned by the &amp;#34;id_token&amp;#34; and &amp;#34;user_info&amp;#34; files. This allows for a very wide range of vulnerabilities depending on how clients use claims. For example, if some clients rely on an email field to identify a user, an attacker can choose the email address they want, and therefore assume any identity they choose. Version 16.0.0 fixes the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-64099</guid>
    </item>
  </channel>
</rss>
