dockerspawner is a tool to spawn JupyterHub single user servers in Docker containers. Users of JupyterHub deployments running DockerSpawner starting with 0.11.0 without specifying `DockerSpawner.allowed_images` configuration allow users to launch _any_ pullable docker image, instead of restricting to only the single configured image, as intended. This issue has been addressed in commit `3ba4b665b` which has been included in dockerspawner release version 13. Users are advised to upgrade. Users unable to upgrade should explicitly set `DockerSpawner.allowed_images` to a non-empty list containing only the default image will result in the intended default behavior.
References
Configurations
History
21 Nov 2024, 08:31
Type | Values Removed | Values Added |
---|---|---|
CVSS |
v2 : v3 : |
v2 : unknown
v3 : 8.0 |
References | () https://github.com/jupyterhub/dockerspawner/commit/3ba4b665b6ca6027ea7a032d7ca3eab977574626 - Patch | |
References | () https://github.com/jupyterhub/dockerspawner/security/advisories/GHSA-hfgr-h3vc-p6c2 - Vendor Advisory |
13 Dec 2023, 18:39
Type | Values Removed | Values Added |
---|---|---|
New CVE |
Information
Published : 2023-12-08 20:15
Updated : 2024-11-21 08:31
NVD link : CVE-2023-48311
Mitre link : CVE-2023-48311
CVE.ORG link : CVE-2023-48311
JSON object : View
Products Affected
jupyter
- dockerspawner
CWE