Dockerspawner
Approved changes feed: RSS · Atom
cpe:2.3:a:jupyterhub:dockerspawner:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Jupyterhub (b9fc67de-411f-5996-aa79-a32cff5a7e29) |
|---|---|
| Product | Dockerspawner (68508e72-7368-5a47-b2cd-82307a27c638) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2023-48311 |
vulnerable | 2026-06-08 06:14:26.856322 |
Any image allowed by default
HIGH (8)
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.
Published: 2023-12-08T20:08:31.736Z
Updated: 2024-08-02T21:23:39.501Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.