Unauthorized login via bypassed identity-provider restriction
Published Jun 12, 2024 · Updated Aug 2, 2024
Authorization bypass in Project Jupyter OAuthenticator before 16.3.1 allows remote authenticated users to bypass institutional login limits. GlobusOAuthenticator evaluates the identity_provider restriction in check_allowed, after JupyterHub 5.0's allow_all decision has already granted access. Exposure requires JupyterHub 5.0, Globus authentication, allow_all enabled, and an identity_provider restriction; any valid Globus user can then access the hub regardless of institution.
Summary
What happened
Authorization bypass in Project Jupyter OAuthenticator before 16.3.1 allows remote authenticated users to bypass institutional login limits. GlobusOAuthenticator evaluates the identity_provider restriction in check_allowed, after JupyterHub 5.0's allow_all decision has already granted access. Exposure requires JupyterHub 5.0, Globus authentication, allow_all enabled, and an identity_provider restriction; any valid Globus user can then access the hub regardless of institution.
The record
- CVE
- CVE-2024-37300
- Published
- Jun 12, 2024
- Updated
- Aug 2, 2024
- Vendor
- Project Jupyter
- Product
- OAuthenticator
- Classifications
- CWE-863, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 12, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 16.3.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo