PyCrypto does not properly reseed PRNG before allowing access
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2013-1445US | medium4.3 | — | ||
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 ma… | ||||
02
references
External citations — patches, advisories, analysis.
- http://www.debian.org/security/2013/dsa-2781WEB
- http://www.openwall.com/lists/oss-security/2013/10/17/3WEB
- https://github.com/dlitz/pycrypto/commit/19dcf7b15d61b7dc1a125a367151de40df6ef175WEB
- https://github.com/pycrypto/pycryptoPACKAGE
- https://github.com/pypa/advisory-database/tree/main/vulns/pycrypto/PYSEC-2013-29.yamlWEB
- https://nvd.nist.gov/vuln/detail/CVE-2013-1445ADVISORY
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan