First published: Sat Oct 26 2013(Updated: )
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.
Credit: security@debian.org security@debian.org
Affected Software | Affected Version | How to fix |
---|---|---|
pip/pycrypto | <2.6.1 | 2.6.1 |
SUSE Python-pycrypto | <=2.6 | |
SUSE Python-pycrypto | =1.0.0 | |
SUSE Python-pycrypto | =1.0.1 | |
SUSE Python-pycrypto | =1.0.2 | |
SUSE Python-pycrypto | =2.0 | |
SUSE Python-pycrypto | =2.0.1 | |
SUSE Python-pycrypto | =2.1.0 | |
SUSE Python-pycrypto | =2.2 | |
SUSE Python-pycrypto | =2.3 | |
SUSE Python-pycrypto | =2.4 | |
SUSE Python-pycrypto | =2.4.1 | |
SUSE Python-pycrypto | =2.5 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2013-1445 has a medium severity rating due to the potential for sensitive information leakage.
To mitigate CVE-2013-1445, upgrade PyCrypto to version 2.6.1 or later.
CVE-2013-1445 affects all versions of PyCrypto prior to 2.6.1.
The impact of CVE-2013-1445 involves easier access for attackers to obtain sensitive information due to a race condition.
Yes, a patch is available as part of PyCrypto version 2.6.1, which resolves the vulnerability.