First published: Fri Dec 08 2023(Updated: )
### Impact Users of JupyterHub deployments running DockerSpawner starting with 0.11.0 without specifying `DockerSpawner.allowed_images` configuration allow users to launch _any_ pullable image, instead of restricting to only the single configured image, as intended. ### Patches Upgrade to DockerSpawner 13. ### Workarounds Explicitly setting `DockerSpawner.allowed_images` to a non-empty list containing only the default image will result in the intended default behavior: ```python c.DockerSpawner.image = "your-image" c.DockerSpawner.allowed_images = ["your-image"] ```
Credit: security-advisories@github.com security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Jupyter Dockerspawner | >=0.11.0<13.0 | |
pip/dockerspawner | >=0.11.0<13.0.0 | 13.0.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID of this vulnerability is CVE-2023-48311.
The impact of this vulnerability is that users of JupyterHub deployments running DockerSpawner starting with version 0.11.0 without specifying DockerSpawner.allowed_images configuration can launch any pullable image instead of being restricted to only the single configured image.
To fix this vulnerability, upgrade to DockerSpawner version 13.0.0.
You can find more information about this vulnerability on the GitHub security advisories page: https://github.com/jupyterhub/dockerspawner/security/advisories/GHSA-hfgr-h3vc-p6c2
The CWE ID of this vulnerability is CWE-20.