CVE-2024-37300 Affecting py3-oauthenticator package, versions <16.3.1-r0
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-CHAINGUARDLATEST-PY3OAUTHENTICATOR-7251835
- published13 Jun 2024
- disclosed12 Jun 2024
Introduced: 12 Jun 2024
CVE-2024-37300 (opens in a new tab)How to fix?
Upgrade Chainguard py3-oauthenticator to version 16.3.1-r0 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream py3-oauthenticator package and not the py3-oauthenticator package as distributed by Chainguard.
See How to fix? for Chainguard relevant fixed versions and status.
OAuthenticator is software that allows OAuth2 identity providers to be plugged in and used with JupyterHub. JupyterHub < 5.0, when used with GlobusOAuthenticator, could be configured to allow all users from a particular institution only. This worked fine prior to JupyterHub 5.0, because allow_all did not take precedence over identity_provider. Since JupyterHub 5.0, allow_all does take precedence over identity_provider. On a hub with the same config, now all users will be allowed to login, regardless of identity_provider. identity_provider will basically be ignored. This is a documented change in JupyterHub 5.0, but is likely to catch many users by surprise. OAuthenticator 16.3.1 fixes the issue with JupyterHub 5.0, and does not affect previous versions. As a workaround, do not upgrade to JupyterHub 5.0 when using GlobusOAuthenticator in the prior configuration.