incomplete JupyterHub logout with simultaneous JupyterLab sessions
CVE-2021-41247 · GHSA-cw7p-q79f-m2v7 · published 2021-11-08 · updated 2024-09-24
- Severity
- Medium
- CVSS score
- 3.5
- Chance of exploitation (EPSS)
- 0.80%
- Fixed in
- 1.5.0
Users of JupyterLab with JupyterHub who have multiple JupyterLab tabs open in the same browser session, may see incomplete logout from the single-user server, as fresh credentials (for the single-user server only, not the Hub) reinstated after logout, if another active JupyterLab session is open while the logout takes place.
Upgrade jupyterhub to 1.5.0 or later.
Upgrade to JupyterHub 1.5. For distributed deployments, it is jupyterhub in the user environment that needs patching. There are no patches necessary in the Hub environment.
The only workaround is to make sure that only one JupyterLab tab is open when you log out.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| jupyterhub | PyPI | >= 1.0.0, < 1.5.0 | 1.5.0 |
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLangflow affected by Remote Code Execution via validate_code() exec()langflowExploited
- CriticalJupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routesjupyter-mcp-server
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
- HighJupyterHub has a privilege escalation vulnerability with the `admin:users` scopejupyterhub, jupyterhub
- HighCross site scripting (XSS) in JupyterHub via Self-XSS leveraged by Cookie Tossingjupyterhub
- MediumJupyterHub has Unauthenticated Denial of Service via Unbounded Username Logging on Failed Loginjupyterhub
- MediumJupyterHub has cross-origin form POSTs bypass XSRF (CWE-352)jupyterhub
- MediumJupyterHub has an Open Redirect Vulnerabilityjupyterhub
- MediumCross-Site Request Forgery in JupyterHubjupyterhub
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.