CVE-2013-1445

Description

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.

Severity
not scored
CVSS v3
not scored
Exploit chance (EPSS)
1.738%
chance of exploitation in the next 30 days
higher than 78.1% of scored CVEs · 2026-11-17
CISA KEV
Not listed
Public exploit code
Yes
Exploit references (NVD and CNA): 2
Metasploit modules: 0
Nuclei templates: 0

Weakness

Timeline

  1. 2013-10-26Published by the CNA17:00 UTC
  2. 2022-05-17GitHub advisory published (GHSA-x377-f64p-hf5j)3125 days after publication

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Exploit and advisory records

GitHub advisory GHSA-x377-f64p-hf5j, affected packages:

PackageVulnerable versionsFixed in
PyPI pycryptobefore 2.6.12.6.1

Affected products

Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.

ProductVulnerable versionsFixed in
dlitz pycrypto1.0.0no fix listed1.0.1no fix listed1.0.2no fix listed2.0no fix listed2.0.1no fix listed(+7 more)not listednot listednot listednot listednot listed

Products and versions as NVD and the vendor that published the CVE list them.

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources