Where does the primary responsibility lie regarding the eMudhra CA key compromise?
8 Bits of Trust: The eMudhra CA Key Disaster
A recent security discovery has sent shockwaves through the cybersecurity community, revealing that eight eMudhra intermediate certificate authority (CA) keys were incredibly weak. Instead of the massive, random 384-bit numbers required for P-384 curve security, several keys were found to be trivial integers like 4, 56, and 115. This vulnerability allowed anyone to recover the private keys from public certificates in milliseconds using basic hardware. The impact extended to TLS issuing CAs and code-signing CAs, some of which were cross-signed by Sectigo's AAA Certificate Services. While major browsers like Chrome, Firefox, and Safari have since moved to block or remove these affected certificates, the window of vulnerability was significant, lasting from April 2025 until the discovery. Unlike traditional key thefts where an attacker must physically steal a file, these keys were effectively public from the moment they were created. This incident highlights a critical failure in the cryptographic generation process and raises urgent questions about how the industry monitors for such low-entropy keys before they can be exploited.
Options
- eMudhra, for the catastrophic failure to generate high-entropy keys.
- Sectigo, for providing trust via their cross-signed certificates.
- Browser vendors like Chrome and Firefox, for reactive rather than proactive detection.
- The security community, for lacking automated tools to detect low-entropy certificates.