CVE-2015-5607: PYSEC-2017-47 - Cross-site request forgery in the REST API in IPython 2 and 3.

CVE-2015-5607 · Severity: low · CVSS 3 · Published 2017-09-20

Cross-site request forgery in the REST API in IPython 2 and 3.

Technologies: ipython (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2015-5607 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2015-5607 being exploited in the wild.
How severe is CVE-2015-5607?
Low severity, with a CVSS score of 3, published 20 September 2017.
Which products and versions are affected?
ipython (PyPI) ECOSYSTEM:introduced=0.12,fixed=2.4.1, GIT:introduced=0,fixed=a05fe052a18810e92d9be8c1185952c13fe4e5b0,fixed=1415a9710407e7c14900531813c15ba6165f0816|ECOSYSTEM:introduced=0,fixed=3.2.1.
Is there a fix for CVE-2015-5607?
Yes. ipython (PyPI): upgrade to 2.4.1, 3.2.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2015-5607?
Check whether you run ipython (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

  • ipython (PyPI): upgrade to 2.4.1, 3.2.1 or later
    pip install "ipython>=3.2.1"

Affected products

  • ipython (PyPI) ECOSYSTEM:introduced=0.12,fixed=2.4.1, GIT:introduced=0,fixed=a05fe052a18810e92d9be8c1185952c13fe4e5b0,fixed=1415a9710407e7c14900531813c15ba6165f0816|ECOSYSTEM:introduced=0,fixed=3.2.1

Identifiers

  • CVE-2015-5607
  • GHSA-7fc2-rm35-2pp7
  • PYSEC-2017-47

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