oauthenticator@0.6.1 vulnerabilities

OAuthenticator: Authenticate JupyterHub users with common OAuth providers

Direct Vulnerabilities

Known vulnerabilities in the oauthenticator package. This does not include vulnerabilities belonging to this package’s dependencies.

Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.
Fix for free
Vulnerability Vulnerable Version
  • H
Authentication Bypass

Affected versions of this package are vulnerable to Authentication Bypass that relies on membership in a Google organization/workspace for authentication by matching the GoogleOAuthenticator.hosted_domain. An attacker in possession of an illegitimate email address on a legitimate Google domain can gain unauthorized access to a JupyterHub.

How to fix Authentication Bypass?

Upgrade oauthenticator to version 16.3.0 or higher.

[,16.3.0)
  • M
Authorization Bypass Through User-Controlled Key

Affected versions of this package are vulnerable to Authorization Bypass Through User-Controlled Key when using CILogonOAuthenticator which does not verify which provider is used by the user to login, only the email address provided.

How to fix Authorization Bypass Through User-Controlled Key?

Upgrade oauthenticator to version 15.0.0 or higher.

[,15.0.0)
  • H
Authentication Bypass

oauthenticator is an authenticator package.

Affected versions of this package are vulnerable to Authentication Bypass. When using JupyterHub with GitLab group whitelisting for access control, group membership was not checked correctly, allowing members not in the whitelisted groups to create accounts on the Hub. (Users were not allowed to access other users, accounts, but could create their own accounts on the Hub linked to their GitLab account. GitLab authentication not using gitlab_group_whitelist is unaffected. No other Authenticators are affected.)

How to fix Authentication Bypass?

Upgrade oauthenticator to version 0.6.2, 0.7.3 or higher.

[0.6.0,0.6.2) [0.7.0,0.7.3)