GHSA-hfgr-h3vc-p6c2: Input Validation
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"] ```
| Affected Software | Affected Version | How to fix |
|---|---|---|
| pip/dockerspawner | >=0.11.0<13.0.0 | 13.0.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the impact of GHSA-hfgr-h3vc-p6c2?
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.
How can I fix GHSA-hfgr-h3vc-p6c2 vulnerability?
Upgrade to DockerSpawner version 13.0.0.
- collector/github-advisory-latest
- alias/GHSA-hfgr-h3vc-p6c2
- alias/CVE-2023-48311
- collector/github-advisory
- agent/type
- agent/references
- agent/description
- agent/first-publish-date
- agent/tags
- agent/softwarecombine
- agent/last-modified-date
- agent/event
- agent/severity
- agent/weakness
- package-manager/pip