CVE-2012-2417: n/a vulnerability

CVE-2012-2417: PyCrypto before 2.6 does not produce appropriate prime numbers when using an ElGamal scheme to generate a k...

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.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 6, 2024, 19:34 UTC (UTC+00:00)

Security readout for executives and security teams

PyCrypto before 2.6 could generate weak ElGamal keys because it did not choose appropriate prime numbers. Organizations using those generated keys may have a smaller key space than expected, making private-key brute force more feasible. Exposure is narrow: it depends on legacy PyCrypto and ElGamal key generation use. Most exposure is likely in older Python applications or systems that installed PyCrypto before 2.6 and generated or still trust ElGamal keys created by that version. Treat this as a targeted legacy crypto risk. Prioritize systems that still use PyCrypto-generated ElGamal keys, especially where keys protect sensitive data or signatures. Broad emergency response is not supported by the provided evidence. Mitigation focus: Upgrade PyCrypto to version 2.6 or a vendor-packaged fixed release.; Follow applicable Debian, Fedora, SUSE, or other distribution security advisories.; Identify ElGamal keys generated by vulnerable PyCrypto versions..

Prepared: Jun 24, 2026, 12:34 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2012-2417 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Jun 17, 2012, 01:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

6Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
https://github.com/Legrandin/pycrypto/commit/9f912f13df99ad3421eff360d6a62d7dbec755c2CVE reference · x_refsource_MISC
https://bugs.launchpad.net/pycrypto/+bug/985164CVE reference · x_refsource_MISC
openSUSE-SU-2012:0830CVE reference · vendor-advisory, x_refsource_SUSE
pycrypto-keys-weak-security(75871)CVE reference · vdb-entry, x_refsource_XF
https://github.com/dlitz/pycrypto/blob/373ea760f21701b162e8c4912a66928ee30d401a/ChangeLogCVE reference · x_refsource_CONFIRM

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.