CVE-2013-1445: PyCrypto does not properly reseed PRNG before allowing access

CVE-2013-1445 · Severity: low · CVSS 3.1 · Published 2013-10-26

The Crypto.Random.atfork function in PyCrypto before 2.6.1 does not properly reseed the pseudo-random number generator (PRNG) before allowing a child process to access it, which makes it easier for context-dependent attackers to obtain sensitive information by leveraging a race condition in which a child process is created and accesses the PRNG within the same rate-limit period as another process.

Technologies: pycrypto (PyPI). Vendors: PyPI.

Quick answers

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

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

Affected products

  • pycrypto (PyPI) ECOSYSTEM:introduced=0,fixed=2.6.1, GIT:introduced=0,fixed=19dcf7b15d61b7dc1a125a367151de40df6ef175|ECOSYSTEM:introduced=0,fixed=2.6.1

Identifiers

  • CVE-2013-1445
  • GHSA-x377-f64p-hf5j
  • PYSEC-2013-29

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