CVE-2013-1629: Improper Input Validation in pip

CVE-2013-1629 · Severity: low · CVSS 3.1 · Published 2013-08-06

pip before 1.3 uses HTTP to retrieve packages from the PyPI repository, and does not perform integrity checks on package contents, which allows man-in-the-middle attackers to execute arbitrary code via a crafted response to a "pip install" operation.

Technologies: pip (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2013-1629 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2013-1629 being exploited in the wild.
How severe is CVE-2013-1629?
Low severity, with a CVSS score of 3.1, published 6 August 2013.
Which products and versions are affected?
pip (PyPI) ECOSYSTEM:introduced=0,fixed=1.3.
Is there a fix for CVE-2013-1629?
Yes. pip (PyPI): upgrade to 1.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2013-1629?
Check whether you run pip (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

  • pip (PyPI): upgrade to 1.3 or later
    pip install "pip>=1.3"

Affected products

  • pip (PyPI) ECOSYSTEM:introduced=0,fixed=1.3

Identifiers

  • CVE-2013-1629
  • GHSA-g3p5-fjj9-h8gj
  • PYSEC-2013-8

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