Cloudflare tracks exploitation of eMudhra's critically weak CA keys

Cloudflare has released a technical follow-up regarding the unprecedented security failure at Certificate Authority (CA) eMudhra. The incident involved the generation of eight extremely weak intermediate private keys—some as simple as the number 4—due to a suspected error in a key generation script. Because these keys are mathematically trivial, they can be recovered almost instantly from public certificates, enabling attackers to bypass TLS security for any domain.

Cloudflare has successfully patched its high-priority systems, including its Pingora-based outbound proxies, to reject these vulnerable keys. While Cloudflare has observed approximately 22,000 attempted handshakes using the weak keys, including forged certificates targeting various organizations and IoT domains, they have found no evidence of successful interception of their own traffic. eMudhra has announced it is exiting the public CA business following the discovery.

Technical breakdown of the eMudhra key failure

• Key Vulnerability: The intermediate private keys were mathematically weak (e.g., values like 4, 56, 66, 115, 155, 156, 230, and 237), allowing for near-instant recovery from public certificates.
• Attack Vector: Attackers can use the recovered keys to create forged certificates for any domain, which unpatched clients that do not enforce Certificate Transparency (CT) will accept.
• Mitigation Strategy: Cloudflare utilized AI-assisted source code analysis to identify all internal systems trusting the keys and deployed patches to its Pingora proxies within hours to reject the vulnerable certificates.
• Exploitation Evidence: Cloudflare logged roughly 22,000 handshake attempts; while many were tests, approximately 160 involved forged certificates with Subject Alternative Names (SANs) targeting unrelated organizations and consumer IoT devices.
• Detection Method: To gauge visitor vulnerability, Cloudflare used JavaScript-enabled challenge pages to perform probe connections using both eMudhra-signed and standard certificates to see which clients still trusted the weak keys.

Why it matters

This incident highlights a catastrophic failure in the CA trust model, where a single script error can compromise the integrity of the global TLS ecosystem. System administrators and software engineers must ensure their clients strictly enforce Certificate Transparency and maintain up-to-date root and intermediate certificate stores to prevent man-in-the-middle attacks from forged certificates.