CVE-2024-41942: JupyterHub has a privilege escalation vulnerability with the `admin:users` scope
First published: Thu Aug 08 2024(Updated: )
### Summary If a user is granted the `admin:users` scope, they may escalate their own privileges by making themselves a full admin user. ### Details The `admin:users` scope allows a user to edit user records: > admin:users > > Read, write, create and delete users and their authentication state, not including their servers or tokens. > > -- https://jupyterhub.readthedocs.io/en/stable/rbac/scopes.html#available-scopes However, this includes making users admins. Admin users are granted scopes beyond `admin:users` making this a mechanism by which granted scopes may be escalated. ### Impact 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.
Credit: security-advisories@github.com security-advisories@github.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Jupyter JupyterHub | <4.1.6 | |
| Jupyter JupyterHub | =5.0.0 | |
| Jupyter JupyterHub | =5.0.0-beta1 | |
| Jupyter JupyterHub | =5.0.0-beta2 | |
| pip/jupyterhub | >=5.0.0<5.1.0 | 5.1.0 |
| pip/jupyterhub | <4.1.6 | 4.1.6 |
| IBM Cognos Analytics | <=12.0.0-12.0.4 | |
| IBM Cognos Analytics | <=11.2.0-11.2.4 FP4 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://github.com/jupyterhub/jupyterhub/security/advisories/GHSA-9x4q-3gxw-849f
- https://github.com/jupyterhub/jupyterhub/commit/99e2720b0fc626cbeeca3c6337f917fdacfaa428
- https://github.com/jupyterhub/jupyterhub/commit/ff2db557a85b6980f90c3158634bf924063ab8ba
- https://nvd.nist.gov/vuln/detail/CVE-2024-41942
- https://github.com/pypa/advisory-database/tree/main/vulns/jupyterhub/PYSEC-2024-200.yaml
- https://github.com/advisories/GHSA-9x4q-3gxw-849f (Advisory)
- https://www.ibm.com/support/pages/node/7181480 (Advisory)
Frequently Asked Questions
What is the severity of CVE-2024-41942?
CVE-2024-41942 has a critical severity level due to the potential for privilege escalation.
How do I fix CVE-2024-41942?
To remediate CVE-2024-41942, upgrade to JupyterHub version 5.1.0 or above.
Which software versions are affected by CVE-2024-41942?
CVE-2024-41942 affects JupyterHub versions up to 5.0.0 and below, including several beta versions.
What type of vulnerability is CVE-2024-41942?
CVE-2024-41942 is a privilege escalation vulnerability.
Can users without admin:users scope exploit CVE-2024-41942?
Yes, users who have been granted the admin:users scope can exploit CVE-2024-41942 to escalate their privileges.
- agent/title
- agent/weakness
- agent/type
- agent/first-publish-date
- agent/severity
- agent/description
- agent/author
- collector/mitre-cve
- source/MITRE
- agent/remedy
- agent/event
- collector/nvd-cve
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/nvd-api
- agent/softwarecombine
- agent/trending
- agent/source
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-9x4q-3gxw-849f
- alias/CVE-2024-41942
- agent/last-modified-date
- agent/references
- agent/tags
- collector/github-advisory
- collector/ibm-support
- source/IBM
- vendor/jupyter
- canonical/jupyter jupyterhub
- version/jupyter jupyterhub/5.0.0
- version/jupyter jupyterhub/5.0.0-beta1
- version/jupyter jupyterhub/5.0.0-beta2
- package-manager/pip
- vendor/ibm
- canonical/ibm cognos analytics
- version/ibm cognos analytics/12.0.0-12.0.4
- version/ibm cognos analytics/11.2.0-11.2.4 fp4