<?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, 18 Nov 2026 02:47:26 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-31027 — Authorization Bypass Through User-Controlled Key when using CILogonOAuthenticator in oauthenticator</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2022-31027</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; jupyterhub oauthenticator&lt;/p&gt;
&lt;p&gt;OAuthenticator is an OAuth token library for the JupyerHub login handler. CILogonOAuthenticator is provided by the OAuthenticator package, and lets users log in to a JupyterHub via CILogon. This is primarily used to restrict a JupyterHub only to users of a given institute. The allowed_idps configuration trait of CILogonOAuthenticator is documented to be a list of domains that indicate the institutions whose users are authorized to access this JupyterHub. This authorization is validated by ensuring that the *email* field provided to us by CILogon has a *domain* that matches one of the domains listed in `allowed_idps`.If `allowed_idps` contains `berkeley.edu`, you might expect only users with valid current credentials provided by University of California, Berkeley to be able to access the JupyterHub. However, CILogonOAuthenticator does *not* verify which provider is used by the user to login, only the email address provided. So a user can login with a GitHub account that has email set to `&amp;lt;something&amp;gt;@berkeley.edu`, and that will be treated exactly the same as someone logging in using the UC Berkeley official Identity Provider. The patch fixing this issue makes a *breaking change* in how `allowed_idps` is interpreted. It&amp;#39;s no longer a list of domains, but configuration representing the `EntityID` of the IdPs that are allowed, picked from the [list maintained by CILogon](https://cilogon.org/idplist/). Users are advised to upgrade.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; jupyterhub oauthenticator&lt;/p&gt;
&lt;p&gt;OAuthenticator is an OAuth token library for the JupyerHub login handler. CILogonOAuthenticator is provided by the OAuthenticator package, and lets users log in to a JupyterHub via CILogon. This is primarily used to restrict a JupyterHub only to users of a given institute. The allowed_idps configuration trait of CILogonOAuthenticator is documented to be a list of domains that indicate the institutions whose users are authorized to access this JupyterHub. This authorization is validated by ensuring that the *email* field provided to us by CILogon has a *domain* that matches one of the domains listed in `allowed_idps`.If `allowed_idps` contains `berkeley.edu`, you might expect only users with valid current credentials provided by University of California, Berkeley to be able to access the JupyterHub. However, CILogonOAuthenticator does *not* verify which provider is used by the user to login, only the email address provided. So a user can login with a GitHub account that has email set to `&amp;lt;something&amp;gt;@berkeley.edu`, and that will be treated exactly the same as someone logging in using the UC Berkeley official Identity Provider. The patch fixing this issue makes a *breaking change* in how `allowed_idps` is interpreted. It&amp;#39;s no longer a list of domains, but configuration representing the `EntityID` of the IdPs that are allowed, picked from the [list maintained by CILogon](https://cilogon.org/idplist/). Users are advised to upgrade.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2022-31027</guid>
    </item>
    <item>
      <title>GHSA-r7v4-jwx9-wx43 — Authorization Bypass Through User-Controlled Key when using CILogonOAuthenticator oauthenticator</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-r7v4-jwx9-wx43</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: oauthenticator&lt;/p&gt;
&lt;p&gt;# Background&lt;/p&gt;
&lt;p&gt;CILogon is a federated auth provider that allows users to authenticate
themselves via a number of Identity Providers (IdP), focused primarily on educational and
research institutions (such as Universities). More traditional and open IdPs
such as GitHub, ORCID, Google, Microsoft, etc are also supported.&lt;/p&gt;
&lt;p&gt;CILogonOAuthenticator is provided by the OAuthenticator package, and lets users log
in to a JupyterHub via CILogon. This is primarily used to restrict a JupyterHub
only to users of a given institute. The allowed_idps configuration trait of
CILogonOAuthenticator is documented to be a list of domains that indicate the
institutions whose users are authorized to access this JupyterHub. This authorization
is validated by ensuring that the *email* field provided to us by CILogon has a
*domain* that matches one of the domains listed in `allowed_idps`.&lt;/p&gt;
&lt;p&gt;# Impact&lt;/p&gt;
&lt;p&gt;If `allowed_idps` contains `berkeley.edu`, you might expect only users with valid
current credentials provided by University of California, Berkeley to be able to
access the JupyterHub. However, CILogonOAuthenticator does *not* verify which provider
is used by the user to login, only the email address provided. So a user can login
with a GitHub account that has email set to `&amp;lt;something&amp;gt;@berkeley.edu`, and that will
be treated exactly the same as someone logging in using the UC Berkeley official
Identity Provider. This has two consequences:&lt;/p&gt;
&lt;p&gt;1. Since GitHub (and most other providers we tested) only require you t…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: oauthenticator&lt;/p&gt;
&lt;p&gt;# Background&lt;/p&gt;
&lt;p&gt;CILogon is a federated auth provider that allows users to authenticate
themselves via a number of Identity Providers (IdP), focused primarily on educational and
research institutions (such as Universities). More traditional and open IdPs
such as GitHub, ORCID, Google, Microsoft, etc are also supported.&lt;/p&gt;
&lt;p&gt;CILogonOAuthenticator is provided by the OAuthenticator package, and lets users log
in to a JupyterHub via CILogon. This is primarily used to restrict a JupyterHub
only to users of a given institute. The allowed_idps configuration trait of
CILogonOAuthenticator is documented to be a list of domains that indicate the
institutions whose users are authorized to access this JupyterHub. This authorization
is validated by ensuring that the *email* field provided to us by CILogon has a
*domain* that matches one of the domains listed in `allowed_idps`.&lt;/p&gt;
&lt;p&gt;# Impact&lt;/p&gt;
&lt;p&gt;If `allowed_idps` contains `berkeley.edu`, you might expect only users with valid
current credentials provided by University of California, Berkeley to be able to
access the JupyterHub. However, CILogonOAuthenticator does *not* verify which provider
is used by the user to login, only the email address provided. So a user can login
with a GitHub account that has email set to `&amp;lt;something&amp;gt;@berkeley.edu`, and that will
be treated exactly the same as someone logging in using the UC Berkeley official
Identity Provider. This has two consequences:&lt;/p&gt;
&lt;p&gt;1. Since GitHub (and most other providers we tested) only require you t…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-r7v4-jwx9-wx43</guid>
    </item>
  </channel>
</rss>
