<?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://vulnerability.circl.lu</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>Fri, 09 Oct 2026 08:28:45 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2024-21632</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2024-21632</link>
      <description>&lt;p&gt;omniauth-microsoft_graph provides an Omniauth strategy for the Microsoft Graph API. Prior to versions 2.0.0, the implementation did not validate the legitimacy of the `email` attribute of the user nor did it give/document an option to do so, making it susceptible to nOAuth misconfiguration in cases when the `email` is used as a trusted user identifier. This could lead to account takeover. Version 2.0.0 contains a fix for this issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;omniauth-microsoft_graph provides an Omniauth strategy for the Microsoft Graph API. Prior to versions 2.0.0, the implementation did not validate the legitimacy of the `email` attribute of the user nor did it give/document an option to do so, making it susceptible to nOAuth misconfiguration in cases when the `email` is used as a trusted user identifier. This could lead to account takeover. Version 2.0.0 contains a fix for this issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2024-21632</guid>
    </item>
    <item>
      <title>GHSA-5g66-628f-7cvj — Omniauth::MicrosoftGraph Account takeover (nOAuth)</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-5g66-628f-7cvj</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: omniauth-microsoft_graph&lt;/p&gt;
&lt;p&gt;### Summary
The implementation did not validate the legitimacy of the `email` attribute of the user nor did it give/document an option to do so, making it susceptible to [nOAuth](https://www.descope.com/blog/post/noauth) misconfiguration in cases when the `email` is used as a trusted user identifier&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: omniauth-microsoft_graph&lt;/p&gt;
&lt;p&gt;### Summary
The implementation did not validate the legitimacy of the `email` attribute of the user nor did it give/document an option to do so, making it susceptible to [nOAuth](https://www.descope.com/blog/post/noauth) misconfiguration in cases when the `email` is used as a trusted user identifier&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-5g66-628f-7cvj</guid>
    </item>
    <item>
      <title>gsd-2024-21632</title>
      <link>https://vulnerability.circl.lu/vuln/gsd-2024-21632</link>
      <description>gsd-2024-21632</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/gsd-2024-21632</guid>
    </item>
  </channel>
</rss>
