First published: Wed Dec 09 2020(Updated: )
### Impact user API tokens issued to single-user servers are specified in the environment of systemd units, which are accessible to all users. In particular, the-littlest-jupyterhub is affected, which uses systemdspawner by default. ### Patches Patched in jupyterhub-systemdspawner v0.15 ### Workarounds No workaround other than upgrading systemdspawner to 0.15 ### For more information If you have any questions or comments about this advisory: * Open a thread in [the Jupyter forum](https://discourse.jupyter.org) * Email us at [security@ipython.org](mailto:security@ipython.org)
Credit: security-advisories@github.com security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
pip/jupyterhub-systemdspawner | <0.15.0 | 0.15.0 |
IBM Cognos Analytics | <=12.0.0-12.0.3 | |
IBM Cognos Analytics | <=11.2.0-11.2.4 FP4 | |
JupyterHub systemdspawner | <0.15 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-26261 is a vulnerability in jupyterhub-systemdspawner that allows unauthorized access to user API tokens.
CVE-2020-26261 affects JupyterHub by incorrectly exposing user API tokens to all users.
The severity of CVE-2020-26261 is high with a CVSS score of 7.9.
To fix CVE-2020-26261, update jupyterhub-systemdspawner to version 0.15 or newer.
You can find more information about CVE-2020-26261 in the official GitHub repository of jupyterhub-systemdspawner.