JupyterHub has a privilege escalation vulnerability with the `admin:users` scope
CVE-2024-41942 · GHSA-9x4q-3gxw-849f · published 2024-08-08 · updated 2025-01-21
- Severity
- High
- CVSS score
- 7.2
- Chance of exploitation (EPSS)
- 0.59%
- Fixed in
- 5.1.0
- Exploitation No known exploitation
- Automatable No
- Technical impact Partial
- CISA SSVC
The impact is relatively small in that admin:users is already an extremely privileged scope only granted to trusted users. In effect, admin:users is equivalent to admin=True, which is not intended. Note that the change here only prevents escalation to the built-in JupyterHub admin role that has unrestricted permissions. It does not prevent users with e.g. groups permissions from granting themselves or other users permissions via group membership, which is intentional.
Upgrade jupyterhub to 5.1.0 or later.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| jupyterhub | PyPI | < 4.1.6 | 4.1.6 |
| jupyterhub | PyPI | >= 5.0.0, < 5.1.0 | 5.1.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
- 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
- Mediumincomplete JupyterHub logout with simultaneous JupyterLab sessionsjupyterhub
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.