CVE-2020-36191: Cross-Site Request Forgery in JupyterHub

CVE-2020-36191 · Severity: low · CVSS 3.1 · Published 2021-01-13

JupyterHub 1.1.0 allows CSRF in the admin panel via a request that lacks an _xsrf field, as demonstrated by a /hub/api/user request (to add or remove a user account).

Technologies: jupyterhub (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2020-36191 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2020-36191 being exploited in the wild.
How severe is CVE-2020-36191?
Low severity, with a CVSS score of 3.1, published 13 January 2021.
Which products and versions are affected?
jupyterhub (PyPI) ECOSYSTEM:introduced=0,fixed=1.2.0b1.
Is there a fix for CVE-2020-36191?
Yes. jupyterhub (PyPI): upgrade to 1.2.0b1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2020-36191?
Check whether you run jupyterhub (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • jupyterhub (PyPI): upgrade to 1.2.0b1 or later
    pip install "jupyterhub>=1.2.0b1"

Affected products

  • jupyterhub (PyPI) ECOSYSTEM:introduced=0,fixed=1.2.0b1

Identifiers

  • CVE-2020-36191
  • GHSA-7xx3-qp5w-fw96
  • PYSEC-2021-67

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.