Persistent single-user access via shared PageConfig token
Published Nov 4, 2021 · Updated Aug 4, 2024
Insufficient session expiration in JupyterHub 1.0.0 through 1.4.2 allows remote authenticated users to retain single-user access. JupyterLab loads JUPYTERHUB_API_TOKEN into shared PageConfig data, so another open tab can restore fresh single-user credentials after logout. The condition requires multiple JupyterLab tabs in one browser session; Hub authentication ends, but the browser retains access to the user's server.
Summary
What happened
Insufficient session expiration in JupyterHub 1.0.0 through 1.4.2 allows remote authenticated users to retain single-user access. JupyterLab loads JUPYTERHUB_API_TOKEN into shared PageConfig data, so another open tab can restore fresh single-user credentials after logout. The condition requires multiple JupyterLab tabs in one browser session; Hub authentication ends, but the browser retains access to the user's server.
The record
- CVE
- CVE-2021-41247
- Published
- Nov 4, 2021
- Updated
- Aug 4, 2024
- Vendor
- Project Jupyter
- Product
- JupyterHub
- Classifications
- CWE-613
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 4, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=>= 1.0.0, < 1.5.0 - jupyterhub (pip)
- Affected versionversion=< 1.2.0 - jupyterhub (helm)
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
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