CVE-2024-41942 json
JupyterHub has a privilege escalation vulnerability with the `admin:users` scope
published 2024-08-08 2 y ago modified 2026-09-10 1 mo ago also BIT-jupyterhub-2024-41942 , EUVD-2024-0080 , GHSA-9x4q-3gxw-849f , PYSEC-2024-200
- cvss
- 7.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 48%
- public exploits
- 0
- none known
Summary
JupyterHub is software that allows one to create a multi-user server for Jupyter notebooks. Prior to versions 4.1.6 and 5.1.0, if a user is granted the `admin:users` scope, they may escalate their own privileges by making themselves a full admin user. 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. Versions 4.1.6 and 5.1.0 fix this issue.
Patch / fix
- pypi jupyterhub 4.1.6, 5.1.0
- bitnami jupyterhub 4.1.6, 5.1.0
- jupyter jupyterhub 4.1.6, 5.1.0
- jupyterhub Debian 14, Debian 13 5.2.1+ds1-1
debian advisories DEBIAN-CVE-2024-41942
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.59% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
| OSV | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | jupyterhub | <4.1.6 >=5.0.0, <5.1.0 |
4.1.6 5.1.0 |
| bitnami | jupyterhub | <4.1.6 >=5.0.0, <5.1.0 |
4.1.6 5.1.0 |
Affected products
- jupyterhub jupyterhub
Classification
- Weakness
-
- CWE-274 Improper Handling of Insufficient Privileges
References
-
github.com
/jupyterhub/jupyterhub/commit/99e2720b0fc626cbeeca3c6337f917fdacfaa428
web, patch
-
github.com
/jupyterhub/jupyterhub/commit/ff2db557a85b6980f90c3158634bf924063ab8ba
web, patch
-
github.com
/jupyterhub/jupyterhub/security/advisories/GHSA-9x4q-3gxw-849f
web, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2024-41942
advisory, web
-
github.com
/jupyterhub/jupyterhub
package
-
github.com
/pypa/advisory-database/tree/main/vulns/jupyterhub/PYSEC-2024-200.yaml
web
Sources
- CVE List CVE-2024-41942
- GitHub Advisory GHSA-9x4q-3gxw-849f
- NVD CVE-2024-41942
- OSV BIT-jupyterhub-2024-41942
- OSV PYSEC-2024-200
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.