Skip to content

GoogleOAuthenticator.hosted_domain incorrectly verifies membership of an Google organization/workspace

High severity GitHub Reviewed Published Mar 20, 2024 in jupyterhub/oauthenticator • Updated Mar 30, 2024

Package

pip oauthenticator (pip)

Affected versions

< 16.3.0

Patched versions

16.3.0

Description

Summary and impact

GoogleOAuthenticator.hosted_domain is used to restrict what Google accounts can be authorized to access a JupyterHub. The restriction is intended to ensure Google accounts are part of one or more Google organizations/workspaces verified to control specified domain(s).

The vulnerability is that the actual restriction has been to Google accounts with emails ending with the domain. Such accounts could have been created by anyone which at one time was able to read an email associated with the domain. This was described by Dylan Ayrey (@dxa4481) in this blog post from 15th December 2023.

Remediation

Upgrade to oauthenticator>=16.3.0 or restrict who can login another way, such as allowed_users or allowed_google_groups.

References

@consideRatio consideRatio published to jupyterhub/oauthenticator Mar 20, 2024
Published to the GitHub Advisory Database Mar 20, 2024
Reviewed Mar 20, 2024
Published by the National Vulnerability Database Mar 20, 2024
Last updated Mar 30, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

EPSS score

0.045%
(17th percentile)

Weaknesses

CVE ID

CVE-2024-29033

GHSA ID

GHSA-55m3-44xf-hg4h

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.