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.
No analysis available yet.
No remediation available yet.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
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 |
GHSA-9x4q-3gxw-849f | JupyterHub has a privilege escalation vulnerability with the `admin:users` scope |
Mon, 12 Aug 2024 16:15:00 +0000
| 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 |
Thu, 08 Aug 2024 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 08 Aug 2024 14:45:00 +0000
| 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
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2024-08-08T15:17:06.179Z
Reserved: 2024-07-24T16:51:40.945Z
Link: CVE-2024-41942
Updated: 2024-08-08T15:16:40.250Z
Status : Analyzed
Published: 2024-08-08T15:15:17.527
Modified: 2024-08-12T15:53:27.457
Link: CVE-2024-41942
No data.
OpenCVE Enrichment
No data.
EUVD
Github GHSA