pysec-2013-29
Vulnerability from pysec
Published
2013-10-26 17:55
Modified
2021-08-27 03:22
Details
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.
Impacted products
Name | purl | pycrypto | pkg:pypi/pycrypto |
---|
Aliases
{ "affected": [ { "package": { "ecosystem": "PyPI", "name": "pycrypto", "purl": "pkg:pypi/pycrypto" }, "ranges": [ { "events": [ { "introduced": "0" }, { "fixed": "19dcf7b15d61b7dc1a125a367151de40df6ef175" } ], "repo": "https://github.com/dlitz/pycrypto", "type": "GIT" }, { "events": [ { "introduced": "0" }, { "fixed": "2.6.1" } ], "type": "ECOSYSTEM" } ], "versions": [ "1.9a2", "1.9a5", "1.9a6", "2.0", "2.0.1", "2.1.0", "2.2", "2.3", "2.4", "2.4.1", "2.5", "2.6" ] } ], "aliases": [ "CVE-2013-1445" ], "details": "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.", "id": "PYSEC-2013-29", "modified": "2021-08-27T03:22:16.634811Z", "published": "2013-10-26T17:55:00Z", "references": [ { "type": "FIX", "url": "https://github.com/dlitz/pycrypto/commit/19dcf7b15d61b7dc1a125a367151de40df6ef175" }, { "type": "ADVISORY", "url": "http://www.debian.org/security/2013/dsa-2781" }, { "type": "WEB", "url": "http://www.openwall.com/lists/oss-security/2013/10/17/3" } ] }
Loading…
Loading…
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…