CVE-2024-29033 GoogleOAuthenticator.hosted_domain incorrectly verifies membership of an Google organization/workspace
Attackers can bypass domain restrictions in GoogleOAuthenticator by using email addresses that merely end with the allowed domain, gaining unauthorized access.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2024-29033?
CVE-2024-29033 is a high-severity authentication bypass vulnerability in jupyterhub oauthenticator, published on 20 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
OAuthenticator provides plugins for JupyterHub to use common OAuth providers, as well as base classes for writing one's own Authenticators with any OAuth 2.0 provider. `GoogleOAuthenticator.hosted_domain` is used to restrict what Google accounts can be authorized access to a JupyterHub. The restriction is intented to be to Google accounts part of one or more Google organization verified to control specified domain(s). Prior to version 16.3.0, 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). OAuthenticator 16.3.0 contains a patch for this issue. As a workaround, restrict who can login another way, such as `allowed_users` or `allowed_google_groups`.
Weakness: CWE-285
Which versions are affected by CVE-2024-29033?
3 open source packages ship an affected version, including oauthenticator. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
oauthenticator PyPI | All versions | 16.3.0 |
oauthenticator PyPI | All versions | 16.3.0 |
oauthenticator PyPI | All versions | 16.3.0 |
Products include Jupyter Oauthenticator.
How do I fix CVE-2024-29033?
Upgrade oauthenticator to 16.3.0 or later.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2024-29033 being exploited?
There is no known exploitation of CVE-2024-29033 in the wild and no public exploit code.
Other vulnerabilities in jupyterhub oauthenticator
- CVE-2026-33175 OAuthenticator: Authentication Bypass in Auth0OAuthenticator via Unverified Email Claims
- CVE-2018-7206 JupyterHub OAuthenticator elevation of privilege
- CVE-2020-26250 Base class whitelist configuration ignored in OAuthenticator
- CVE-2022-31027 Authorization Bypass Through User-Controlled Key when using CILogonOAuthenticator in oauthenticator
Sources
Also known as GHSA-55m3-44xf-hg4h, PYSEC-2026-1710.