CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
NONE
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
AI Score
Confidence
High
EPSS
Percentile
15.5%
JupyterHub < 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:
# Require users to be using the "foo.horse" identity provider, often an institution or university
c.GlobusAuthenticator.identity_provider = "foo.horse"
# Allow everyone who has that identity provider to log in
c.GlobusAuthenticator.allow_all = True
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.
Do not upgrade to JupyterHub 5.0 when using GlobusOAuthenticator
in the prior configuration.
Vendor | Product | Version | CPE |
---|---|---|---|
jupyter | oauthenticator | * | cpe:2.3:a:jupyter:oauthenticator:*:*:*:*:*:*:*:* |
github.com/advisories/GHSA-gprj-3p75-f996
github.com/jupyterhub/oauthenticator/commit/d1aea05fa89f2beae15ab0fa0b0d071030f79654
github.com/jupyterhub/oauthenticator/security/advisories/GHSA-gprj-3p75-f996
jupyterhub.readthedocs.io/en/stable/howto/upgrading-v5.html#authenticator-allow-all-and-allow-existing-users
nvd.nist.gov/vuln/detail/CVE-2024-37300