<?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>Wed, 07 Oct 2026 11:49:21 +0000</lastBuildDate>
    <item>
      <title>CVE-2020-15222 — Replay of private_key_jwt possible in ORY Fosite</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2020-15222</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; ory fosite&lt;/p&gt;
&lt;p&gt;In ORY Fosite (the security first OAuth2 &amp;amp; OpenID Connect framework for Go) before version 0.31.0, when using &amp;#34;private_key_jwt&amp;#34; authentication the uniqueness of the `jti` value is not checked. When using client authentication method &amp;#34;private_key_jwt&amp;#34;, OpenId specification says the following about assertion `jti`: &amp;#34;A unique identifier for the token, which can be used to prevent reuse of the token. These tokens MUST only be used once, unless conditions for reuse were negotiated between the parties&amp;#34;. Hydra does not seem to check the uniqueness of this `jti` value. This problem is fixed in version 0.31.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; ory fosite&lt;/p&gt;
&lt;p&gt;In ORY Fosite (the security first OAuth2 &amp;amp; OpenID Connect framework for Go) before version 0.31.0, when using &amp;#34;private_key_jwt&amp;#34; authentication the uniqueness of the `jti` value is not checked. When using client authentication method &amp;#34;private_key_jwt&amp;#34;, OpenId specification says the following about assertion `jti`: &amp;#34;A unique identifier for the token, which can be used to prevent reuse of the token. These tokens MUST only be used once, unless conditions for reuse were negotiated between the parties&amp;#34;. Hydra does not seem to check the uniqueness of this `jti` value. This problem is fixed in version 0.31.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2020-15222</guid>
    </item>
  </channel>
</rss>
