python-crypto: PRNG not correctly reseeded in some situations
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
Configuration 1 [-]
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DSA |
DSA-2781-1 | python-crypto security update |
EUVD |
EUVD-2013-0027 | 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. |
Github GHSA |
GHSA-x377-f64p-hf5j | PyCrypto does not properly reseed PRNG before allowing access |
No CVSS v4.0
No CVSS v3.1
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 1.7% (1.738% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.