CVE-2020-15110PYSEC-2020-51GHSA-V7M9-9497-P9GR
Possible pod name collisions in jupyterhub-kubespawner
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 0.12, 0.12.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- jupyterhub kubespawner
fixed in 0.12
- jupyterhub-kubespawnerPyPI
fixed in 0.12.0
- jupyterhub-kubespawnerPyPI
fixed in 0.12.0