JupyterHub has a privilege escalation vulnerability with the `admin:users` scope
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| jupyterhub | jupyterhub | affected |
|
Configuration 1 [-]
|
No data.
No data available yet.
| 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 |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.590% probability within 30 days)
| 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
|
| 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
|