Jupyter Dockerspawner
By the Year
In 2024 there have been 0 vulnerabilities in Jupyter Dockerspawner . Last year Dockerspawner had 1 security vulnerability published. Right now, Dockerspawner is on track to have less security vulnerabilities in 2024 than it did last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2024 | 0 | 0.00 |
| 2023 | 1 | 4.30 |
| 2022 | 0 | 0.00 |
| 2021 | 0 | 0.00 |
| 2020 | 0 | 0.00 |
| 2019 | 0 | 0.00 |
| 2018 | 0 | 0.00 |
It may take a day or so for new Dockerspawner vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Jupyter Dockerspawner Security Vulnerabilities
dockerspawner is a tool to spawn JupyterHub single user servers in Docker containers
CVE-2023-48311
4.3 - Medium
- December 08, 2023
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.
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for Jupyter Dockerspawner or by Jupyter? Click the Watch button to subscribe.
