Your RSA-2048 keys break in 2030. Find every one of them before attackers do.

CVE-2012-2417

CVE-2012-2417 is a CWE-310 vulnerability in dlitz pycrypto. 1 public exploit reference exists, so weaponization risk is real. O3 Security detects and blocks CVE-2012-2417 exploitation at runtime via eBPF exploit-chain detection and L7 egress monitoring, even on unpatched systems.

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…

Published
Jun 17, 2012
Updated
Jun 16, 2026
Affected
0 pkgs
Patched
None yet
Exploits
1 known

EPSS Exploitation Probability

via FIRST.org ↗
2.4%probability of exploitation in next 30 days
Lower Risk82th percentile-0.35%
1.86%2.77%3.69%4.60%4.1%2.4%Feb 26May 26Jul 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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.

Affected Products

1 product · 21 configurations
Application
pycryptodlitz
≤ 2.5
12 versions
1.0.01.0.11.0.21.11.92.02.0.12.1.02.22.32.42.4.1
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Vendor / appliance
  1. Detect

    Inventory every dlitz pycrypto deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

  2. Remediation status

    No patch has shipped for CVE-2012-2417 yet — track the dlitz pycrypto advisory for a fixed release and apply the workarounds below in the meantime.

  3. Mitigate without a patch

    Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

  4. How O3 protects you

    O3 detects and blocks CVE-2012-2417 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2012-2417. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Runtime Protection

Is CVE-2012-2417 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2012-2417 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.