Back to Database
Status published
Medium
CVE-2020-15110
Possible pod name collisions in jupyterhub-kubespawner
Vulnerability Description
In jupyterhub-kubespawner before 0.12, certain usernames will be able to craft particular server names which will grant them access to the default server of other users who have matching usernames. This has been fixed in 0.12.
Impact Analysis
Refer to official advisory for detailed impact metrics.
Remediation
Ensure systems are updated to the latest vendor-supplied patch levels.
THREAT MONITOR
Am I Vulnerable?
Launch our assessment wizard to check if your infrastructure is exposed to • CVE-2020-15110
Credits & Attribution
No credits recorded in the NVD database.
References
More from jupyterhub
View All →CVE-2025-32428
Jupyter Remote Desktop Proxy makes TigerVNC accessible via the network and not just via a UNIX socket as intended
Critical
9
CVE-2024-41942
JupyterHub has a privilege escalation vulnerability with the `admin:users` scope
High
7.2
CVE-2024-37300
Globus `identity_provider` restriction ignored when used with `allow_all` in JupyterHub 5.0
High
8.1
CVE-2024-35225
Jupyter Server Proxy has a reflected XSS issue in host parameter
Critical
9.7
CVE-2024-29033
GoogleOAuthenticator.hosted_domain incorrectly verifies membership of an Google organization/workspace
High
7.5
Affected Vendor
jupyterhub
View all reports →Affected Software
kubespawner
Vulnerable Versions:
< 0.12
Timeline
Official Publish:
July 17th, 2020
Last Modified:
August 4th, 2024
Added to House:
July 21st, 2026
CVSS Vectors
V3:
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N