CVE-2023-48311: Any image allowed by default

Published Dec 8, 2023
·
Updated

Impact

Users of JupyterHub deployments running DockerSpawner starting with 0.11.0 without specifying DockerSpawner.allowedimages 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.allowedimages 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.allowedimages = ["your-image"]

Other sources

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.allowedimages 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.allowedimages to a non-empty list containing only the default image will result in the intended default behavior.

Affected Software

2 affected componentsFixes available
jupyter dockerspawner>=0.11.0<13.0
pip/dockerspawner>=0.11.0<13.0.0
13.0.0

Event History

Dec 8, 2023
Advisory Published
02:42 PM
CVE Published
via MITRE·08:08 PM
Data Sourced
via MITRE·08:08 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the vulnerability ID of this vulnerability?

The vulnerability ID of this vulnerability is CVE-2023-48311.

2

What is the impact of this vulnerability?

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.

3

How can I fix this vulnerability?

To fix this vulnerability, upgrade to DockerSpawner version 13.0.0.

4

Where can I find more information about this vulnerability?

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

5

What is the CWE ID of this vulnerability?

The CWE ID of this vulnerability is CWE-20.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203