Skip to content

DockerSpawner allows any image by default

Moderate severity GitHub Reviewed Published Dec 8, 2023 in jupyterhub/dockerspawner • Updated Dec 13, 2023

Package

pip dockerspawner (pip)

Affected versions

>= 0.11.0, < 13.0.0

Patched versions

13.0.0

Description

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:

c.DockerSpawner.image = "your-image"
c.DockerSpawner.allowed_images = ["your-image"]

References

@minrk minrk published to jupyterhub/dockerspawner Dec 8, 2023
Published to the GitHub Advisory Database Dec 8, 2023
Reviewed Dec 8, 2023
Published by the National Vulnerability Database Dec 8, 2023
Last updated Dec 13, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

EPSS score

0.053%
(23rd percentile)

Weaknesses

CVE ID

CVE-2023-48311

GHSA ID

GHSA-hfgr-h3vc-p6c2

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.