Unauthorized hub access via email-domain validation
Published Mar 20, 2024 · Updated Aug 2, 2024
Improper authorization in OAuthenticator before 16.3.0 allows remote attackers to access JupyterHub via a crafted Google account. GoogleOAuthenticator.check_allowed trusted the domain suffix parsed from the email claim instead of requiring the Google hd organization claim. Exploitation requires a Google account using an address at the configured hosted domain and grants the JupyterHub access assigned to that identity.
Summary
What happened
Improper authorization in OAuthenticator before 16.3.0 allows remote attackers to access JupyterHub via a crafted Google account. GoogleOAuthenticator.check_allowed trusted the domain suffix parsed from the email claim instead of requiring the Google hd organization claim. Exploitation requires a Google account using an address at the configured hosted domain and grants the JupyterHub access assigned to that identity.
The record
- CVE
- CVE-2024-29033
- Published
- Mar 20, 2024
- Updated
- Aug 2, 2024
- Vendor
- Project Jupyter
- Product
- OAuthenticator
- Classifications
- CWE-285, T1078.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 20, 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.0
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
- Google OAuth email-domain account bypass demonstrationfunctional · demonstrated
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