First published: Sun Jun 17 2012(Updated: )
PyCrypto before 2.6 does not produce appropriate prime numbers when using an ElGamal scheme to generate a key, which reduces the signature space or public key space and makes it easier for attackers to conduct brute force attacks to obtain the private key.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
pip/PyCrypto | <2.6 | 2.6 |
SUSE Python-pycrypto | <=2.5 | |
SUSE Python-pycrypto | =1.0.0 | |
SUSE Python-pycrypto | =1.0.1 | |
SUSE Python-pycrypto | =1.0.2 | |
SUSE Python-pycrypto | =1.1-alpha2 | |
SUSE Python-pycrypto | =1.9-alpha1 | |
SUSE Python-pycrypto | =1.9-alpha2 | |
SUSE Python-pycrypto | =1.9-alpha3 | |
SUSE Python-pycrypto | =1.9-alpha4 | |
SUSE Python-pycrypto | =1.9-alpha5 | |
SUSE Python-pycrypto | =1.9-alpha6 | |
SUSE Python-pycrypto | =2.0 | |
SUSE Python-pycrypto | =2.0.1 | |
SUSE Python-pycrypto | =2.1.0 | |
SUSE Python-pycrypto | =2.1.0-alpha1 | |
SUSE Python-pycrypto | =2.1.0-alpha2 | |
SUSE Python-pycrypto | =2.1.0-beta1 | |
SUSE Python-pycrypto | =2.2 | |
SUSE Python-pycrypto | =2.3 | |
SUSE Python-pycrypto | =2.4 | |
SUSE Python-pycrypto | =2.4.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2012-2417 is considered to have a medium severity due to its potential to enable brute force attacks on generated keys.
To fix CVE-2012-2417, upgrade to PyCrypto version 2.6 or later.
CVE-2012-2417 affects all versions of PyCrypto prior to 2.6.
The impact of CVE-2012-2417 is the potential compromise of private keys due to inadequate prime number generation.
Yes, CVE-2012-2417 can lead to data breaches if attackers successfully obtain the private key through brute force methods.