Strix
26.1K

CVE-2012-2417

UnknownEPSS 2.73%

Last modified

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

Description

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.

Metrics

EPSS Probability
2.73%

84.2th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersionsUpdate
DlitzPycrypto<= 2.5—
DlitzPycrypto1.0.0—
DlitzPycrypto1.0.1—
DlitzPycrypto1.0.2—
DlitzPycrypto1.1Alpha2
DlitzPycrypto1.9Alpha1
DlitzPycrypto2.0—
DlitzPycrypto2.0.1—
DlitzPycrypto2.1.0—
DlitzPycrypto2.2—
DlitzPycrypto2.3—
DlitzPycrypto2.4—
DlitzPycrypto2.4.1—

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2012-2417?
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.
How severe is CVE-2012-2417?
Severity scoring for CVE-2012-2417 is pending analysis. The EPSS model estimates a 2.73% probability of exploitation in the next 30 days.
How do I fix CVE-2012-2417?
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-2012-2417?

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

Scan your code now

Source: NVD / NIST