Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2024-37300— Globus `identity_provider` restriction ignored when used with `allow_all` in JupyterHub 5.0

Quick assessment

Affected
jupyterhub oauthenticator
Exploitation
Public or AI PoC available; prioritize validation
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

OAuthenticator是JupyerHub 登录处理程序的 OAuth 令牌库。 OAuthenticator 16.3.0及之前版本存在安全漏洞，该漏洞源于allow_all配置项在JupyterHub 5.0中开始优先于identity_provider配置项，导致所有用户都能登录，而不考虑identity_provider的设置。

CVSS 8.1 · High EPSS 0.40% · P32
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2024-37300

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Globus `identity_provider` restriction ignored when used with `allow_all` in JupyterHub 5.0
Source: CVE Program / CVE List V5
Vulnerability Description
OAuthenticator is software that allows OAuth2 identity providers to be plugged in and used with JupyterHub. JupyterHub < 5.0, when used with `GlobusOAuthenticator`, could be configured to allow all users from a particular institution only. This worked fine prior to JupyterHub 5.0, because `allow_all` did not take precedence over `identity_provider`. Since JupyterHub 5.0, `allow_all` does take precedence over `identity_provider`. On a hub with the same config, now all users will be allowed to login, regardless of `identity_provider`. `identity_provider` will basically be ignored. This is a documented change in JupyterHub 5.0, but is likely to catch many users by surprise. OAuthenticator 16.3.1 fixes the issue with JupyterHub 5.0, and does not affect previous versions. As a workaround, do not upgrade to JupyterHub 5.0 when using `GlobusOAuthenticator` in the prior configuration.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
授权机制不正确
Source: CVE Program / CVE List V5
Vulnerability Title
OAuthenticator 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
OAuthenticator是JupyerHub 登录处理程序的 OAuth 令牌库。 OAuthenticator 16.3.0及之前版本存在安全漏洞，该漏洞源于allow_all配置项在JupyterHub 5.0中开始优先于identity_provider配置项，导致所有用户都能登录，而不考虑identity_provider的设置。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
jupyterhub oauthenticator < 16.3.1 -

II. Public POCs for CVE-2024-37300

# POC Description Source Link Shenlong Link
AI-Generated POC Premium
Qwen3.6-35B-A3B · 7732 chars
Pro+ exclusive includes:
Vulnerability reproduction recording (real sandbox build + trigger, exclusive)
In-depth vulnerability mechanism
Trigger conditions & impact
Full executable POC code
Exploit chain & mitigation
POC zip download
100+ AI POC generations per month

III. Intelligence Information for CVE-2024-37300

请登录查看更多情报信息。

Patches & Fixes for CVE-2024-37300 (1)

Vendor Advisories for CVE-2024-37300 (1)

Other References for CVE-2024-37300 (1)

IV. Related Vulnerabilities

Same product: oauthenticator
Same vendor: jupyterhub
Same weakness: CWE-863

V. Comments for CVE-2024-37300

No comments yet

Leave a comment