CVE-2020-26250

Published: Dic 01, 2020 Last Modified: Nov 21, 2024 EU-VD ID: EUVD-2020-0118 Aliases: GHSA-384w-5v3f-q499, PYSEC-2020-68
ExploitDB:
Other exploit source:
Google Dorks:
MEDIUM 6,3
Attack Vector: network
Attack Complexity: high
Privileges Required: low
User Interaction: none
Scope: changed
Confidentiality: high
Integrity: none
Availability: none
LOW 3,5
Access Vector: network
Access Complexity: medium
Authentication: single
Confidentiality: partial
Integrity: none
Availability: none

Description

AI Translation Available

OAuthenticator is an OAuth login mechanism for JupyterHub. In oauthenticator from version 0.12.0 and before 0.12.2, the deprecated (in jupyterhub 1.2) configuration `Authenticator.whitelist`, which should be transparently mapped to `Authenticator.allowed_users` with a warning, is instead ignored by OAuthenticator classes, resulting in the same behavior as if this configuration has not been set. If this is the only mechanism of authorization restriction (i.e. no group or team restrictions in configuration) then all authenticated users will be allowed. Provider-based restrictions, including deprecated values such as `GitHubOAuthenticator.org_whitelist` are **not** affected. All users of OAuthenticator 0.12.0 and 0.12.1 with JupyterHub 1.2 (JupyterHub Helm chart 0.10.0-0.10.5) who use the `admin.whitelist.users` configuration in the jupyterhub helm chart or the `c.Authenticator.whitelist` configuration directly. Users of other deprecated configuration, e.g. `c.GitHubOAuthenticator.team_whitelist` are **not** affected. If you see a log line like this and expect a specific list of allowed usernames: '[I 2020-11-27 16:51:54.528 JupyterHub app:1717] Not using allowed_users. Any authenticated user will be allowed.' you are likely affected. Updating oauthenticator to 0.12.2 is recommended. A workaround is to replace the deprecated `c.Authenticator.whitelist = ...` with `c.Authenticator.allowed_users = ...`. If any users have been authorized during this time who should not have been, they must be deleted via the API or admin interface, per the referenced documentation.

EPSS (Exploit Prediction Scoring System)

Trend Analysis

EPSS (Exploit Prediction Scoring System)

Prevede la probabilità di sfruttamento basata su intelligence sulle minacce e sulle caratteristiche della vulnerabilità.

EPSS Score
0,0041
Percentile
0,6th
Updated

EPSS Score Trend (Last 91 Days)

863

Incorrect Authorization

Incomplete
Common Consequences
Security Scopes Affected:
Confidentiality Integrity Access Control Availability
Potential Impacts:
Read Application Data Read Files Or Directories Modify Application Data Modify Files Or Directories Gain Privileges Or Assume Identity Bypass Protection Mechanism Execute Unauthorized Code Or Commands Dos: Crash, Exit, Or Restart Dos: Resource Consumption (Cpu) Dos: Resource Consumption (Memory) Dos: Resource Consumption (Other)
Applicable Platforms
Technologies: Database Server, Not Technology-Specific, Web Server
View CWE Details
Application

Oauthenticator by Jupyter

Version Range Affected
From 0.12.0 (inclusive)
To 0.12.2 (exclusive)
cpe:2.3:a:jupyter:oauthenticator:*:*:*:*:*:*:*:*
Common Platform Enumeration - Standardized vulnerability identification
https://github.com/jupyterhub/oauthenticator/blob/master/docs/source/changelog.…
https://github.com/jupyterhub/oauthenticator/commit/a4aac191c16cf6281f3d346615a…
https://github.com/jupyterhub/oauthenticator/security/advisories/GHSA-384w-5v3f…
https://jupyterhub.readthedocs.io/en/1.2.2/getting-started/authenticators-users…
https://github.com/jupyterhub/oauthenticator/blob/master/docs/source/changelog.…
https://github.com/jupyterhub/oauthenticator/commit/a4aac191c16cf6281f3d346615a…
https://github.com/jupyterhub/oauthenticator/security/advisories/GHSA-384w-5v3f…
https://jupyterhub.readthedocs.io/en/1.2.2/getting-started/authenticators-users…