CVE-2024-29033

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

Severity Score

7.5

*CVSS v3.1

Exploit Likelihood

*EPSS

Affected Versions

*CPE

Public Exploits

*Multiple Sources

Exploited in Wild

*KEV

Decision

Track

*SSVC

Descriptions

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`.

OAuthenticator proporciona complementos para que JupyterHub utilice proveedores de OAuth comunes, así como clases base para escribir sus propios autenticadores con cualquier proveedor de OAuth 2.0. `GoogleOAuthenticator.hosted_domain` se utiliza para restringir a qué cuentas de Google se les puede autorizar el acceso a un JupyterHub. La restricción está destinada a las cuentas de Google que forman parte de una o más organizaciones de Google verificadas para controlar dominios específicos. Antes de la versión 16.3.0, la restricción real era para las cuentas de Google con correos electrónicos que terminaban con el dominio. Estas cuentas podrían haber sido creadas por cualquier persona que en algún momento haya podido leer un correo electrónico asociado con el dominio. Esto fue descrito por Dylan Ayrey (@dxa4481) en esta [publicación de blog] del 15 de diciembre de 2023). OAuthenticator 16.3.0 contiene un parche para este problema. Como workaround, restrinja quién puede iniciar sesión de otra manera, como "usuarios_permitidos" o "grupos_de_google_permitidos".

*Credits: N/A

CVSS Scores

GitHubv3.1 7.5

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

None

* Common Vulnerability Scoring System

SSVC

Decision:Track

Exploitation

None

Automatable

Tech. Impact

Partial

* Organization's Worst-case Scenario

Timeline

2024-03-14 CVE Reserved
2024-03-20 CVE Published
2024-03-21 EPSS Updated
2024-08-02 CVE Updated
---------- Exploited in Wild
---------- KEV Due Date
---------- First Exploit

CWE

CWE-285: Improper Authorization

CAPEC

References (3)

URL	Tag	Source
https://github.com/jupyterhub/oauthenticator/commit/5246b09675501b09fb6ed64022099b7644812f60	X_refsource_misc
https://github.com/jupyterhub/oauthenticator/security/advisories/GHSA-55m3-44xf-hg4h	X_refsource_confirm
https://trufflesecurity.com/blog/google-oauth-is-broken-sort-of	X_refsource_misc

URL	Date	SRC

URL	Date	SRC

URL	Date	SRC

Affected Vendors, Products, and Versions

Vendor		Product				Version		Other		Status
Vendor	Product	Version	Other	Status	<-- -->	Vendor	Product	Version	Other	Status
Jupyterhub Search vendor "Jupyterhub"		Oauthenticator Search vendor "Jupyterhub" for product "Oauthenticator"				< 16.3.0 Search vendor "Jupyterhub" for product "Oauthenticator" and version " < 16.3.0"		en		Affected