CVE-2013-1445

UnknownEPSS 2.01%

Last modified

CVE-2013-1445 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 2.01% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
2.01%

78.3th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
DlitzPycrypto<= 2.6
DlitzPycrypto1.0.0
DlitzPycrypto1.0.1
DlitzPycrypto1.0.2
DlitzPycrypto2.0
DlitzPycrypto2.0.1
DlitzPycrypto2.1.0
DlitzPycrypto2.2
DlitzPycrypto2.3
DlitzPycrypto2.4
DlitzPycrypto2.4.1
DlitzPycrypto2.5

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is 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 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.
How severe is CVE-2013-1445?
Severity scoring for CVE-2013-1445 is pending analysis. The EPSS model estimates a 2.01% probability of exploitation in the next 30 days.
How do I fix CVE-2013-1445?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2013-1445?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST