CVE-2024-41942

JupyterHub has a privilege escalation vulnerability with the `admin:users` scope

Published Aug 8, 2024 CVSS 3.1 · 7.2 High EPSS < 1% KEV · Not listed
Description
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD EUVD EUVD-2024-0080 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.\nIn 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.
Github GHSA Github GHSA GHSA-9x4q-3gxw-849f JupyterHub has a privilege escalation vulnerability with the `admin:users` scope
History
Type Values Removed Values Added
First Time appeared Jupyter
Jupyter jupyterhub
Weaknesses NVD-CWE-noinfo
CPEs cpe:2.3:a:jupyter:jupyterhub:*:*:*:*:*:*:*:*
cpe:2.3:a:jupyter:jupyterhub:5.0.0:-:*:*:*:*:*:*
cpe:2.3:a:jupyter:jupyterhub:5.0.0:beta1:*:*:*:*:*:*
cpe:2.3:a:jupyter:jupyterhub:5.0.0:beta2:*:*:*:*:*:*
Vendors & Products Jupyter
Jupyter jupyterhub
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title JupyterHub has a privilege escalation vulnerability with the `admin:users` scope
Weaknesses CWE-274
References
Metrics cvssV3_1

{'score': 7.2, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 8, 2024, 3:17 PM
Reserved
Jul 24, 2024, 4:51 PM
Status
Analyzed
Published
Aug 8, 2024, 3:15 PM
Modified
Jun 17, 2026, 7:48 AM