CVE-2020-15110
Possible pod name collisions in jupyterhub-kubespawner
HIGH
8.1
CVSS Score
Published: July 17, 2020 at 08:45 PM UTC
Updated: June 17, 2026 at 02:56 AM UTC
1 product affected across 1 vendorKubespawner
Using kubespawner by jupyterhub?
Get instant alerts when new vulnerabilities affect kubespawner - before attackers find them.
Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.1
Exploit prediction
EPSS 1%
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.
Affected
Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.
v < 0.12
Affected range stops below 0.12, so it looks safe — our inference, not a vendor statement
Remediation
No guide yetNo remediation guidance has been written for this CVE yet. What the record does show:
Patch and advisory references
References (2)
x_refsource_CONFIRMPatchThird Party Advisory
Source: [email protected]
https://github.com/jupyterhub/kubespawner/commit/3dfe870a7f5e98e2e398b01996ca6b8eff4bb1d0x_refsource_CONFIRMExploitThird Party Advisory
Source: [email protected]
https://github.com/jupyterhub/kubespawner/security/advisories/GHSA-v7m9-9497-p9grCVSS
- Attack Vector
- NETWORK
- Complexity
- LOW
- Privileges
- LOW
- User Interaction
- NONE
- Scope
- UNCHANGED
- Confidentiality
- HIGH
- Integrity
- HIGH
- Availability
- NONE
Vector?
Quick Info
StatusMODIFIED
CWE
CWE-863
Get alerted
Stop reading CVE feeds looking for your own stack
Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.
Free plan, no card