CVE-2024-37300: Oauthenticator Globus `identity_provider` Restriction Ignored When Vulnerability
HIGHCVE-2024-37300 is a HIGH (CVSS 8.1) globus `identity_provider` restriction ignored when vulnerability (CWE-863: Incorrect Authorization) affecting Oauthenticator libraries in the PyPI ecosystem. The issue involves globus `identity_provider` restriction ignored when used with `allow_all` in jupyterhub 5.0. Remediation is available by upgrading affected packages to version 16.3.1.
CVE-2024-37300 at a Glance
Security Impact
CVSS: 8.1
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N).
How to Fix CVE-2024-37300
To remediate this vulnerability, upgrade all affected Oauthenticator dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
pip install oauthenticator>=16.3.1
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
pip show oauthenticator
How to Check if You Are Affected
To determine whether your Python environment is affected by CVE-2024-37300, inspect your installed packages using pip:
pip show oauthenticator
Analyze the terminal output to locate any version of Oauthenticator in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 16.3.1), your application is affected.
Note: The pip show oauthenticator command checks currently installed packages in your active Python environment.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-863: Incorrect Authorization, where the product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. In Oauthenticator, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2024-37300 Affected Oauthenticator Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
oauthenticator
|
PyPI |
< 16.3.1
|
16.3.1
|
References
Frequently Asked Questions
What is CVE-2024-37300?
Which Oauthenticator versions are affected?
What version fixes CVE-2024-37300?
Is oauthenticator affected?
What is the CVSS score of CVE-2024-37300?
What CWE is associated with CVE-2024-37300?
How can I check PyPI dependencies for CVE-2024-37300?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-gprj-3p75-f996",
"modified" : "2024-06-12T19:24:05Z",
"published" : "2024-06-12T17:13:07Z",
"aliases" : [ "CVE-2024-37300" ],
"summary" : "Globus `identity_provider` restriction ignored when used with `allow_all` in JupyterHub 5.0",
"details" : "### Impact\n\nJupyterHub < 5.0, when used with `GlobusOAuthenticator`, could be configured to allow all users from a particular institution only. The configuration for this would look like:\n\n```python\n# Require users to be using the \"foo.horse\" identity provider, often an institution or university\nc.GlobusAuthenticator.identity_provider = \"foo.horse\"\n# Allow everyone who has that identity provider to log in\nc.GlobusAuthenticator.allow_all = True\n```\n\nThis worked fine prior to JupyterHub 5.0, because `allow_all` *did not* take precedence over `identity_provider`.\n\nSince 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.\n\nThis is a [documented change](https://jupyterhub.readthedocs.io/en/stable/howto/upgrading-v5.html#authenticator-allow-all-and-allow-existing-users) in JupyterHub 5.0,\nbut is likely to catch many users by surprise.\n\n### Patches\n\nOAuthenticator 16.3.1 fixes the issue with JupyterHub 5.0, and does not affect previous versions.\n\n### Workarounds\n\nDo not upgrade to JupyterHub 5.0 when using `GlobusOAuthenticator` in the prior configuration.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "PyPI",
"name" : "oauthenticator"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "16.3.1"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/jupyterhub/oauthenticator/security/advisories/GHSA-gprj-3p75-f996"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2024-37300"
}, {
"type" : "WEB",
"url" : "https://github.com/jupyterhub/oauthenticator/commit/d1aea05fa89f2beae15ab0fa0b0d071030f79654"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/jupyterhub/oauthenticator"
}, {
"type" : "WEB",
"url" : "https://jupyterhub.readthedocs.io/en/stable/howto/upgrading-v5.html#authenticator-allow-all-and-allow-existing-users"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-863" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2024-06-12T17:13:07Z",
"nvd_published_at" : "2024-06-12T16:15:12Z"
}
}