Eight Bits of Trust: eMudhra's CA keys cracked in milliseconds

The crash‑course test in Google’s paranoid_crypto repository broke eMudhra’s CA private keys in milliseconds, proving that a trusted root can be compromised almost instantly. The discovery came from running the tool against the Certificate Authority Database (CCADB) as a quick corpus check. The result shocked the community because the keys were still in active use across many devices.

Paranoid_crypto works by feeding known‑good certificates into a verifier and then attempting to derive the private key from the public parameters; the algorithm succeeded within a few thousand CPU cycles. The CCADB test was intended as a sanity check before examining subscriber certificates, but it revealed that the eMudhra root key material was weak enough to be reconstructed instantly. The underlying weakness appears to be an over‑reliance on a small key space or poor entropy during key generation.

The practical fallout is simple: any system that trusts the compromised CA bundle is now vulnerable to man‑in‑the‑middle attacks. Devices that cannot be patched, especially legacy IoT hardware, are exposed because they still carry the broken CA bundle. The recommendation from the discoverer is to update every package that ships a CA bundle, such as the OS ca‑certificates package and the Python certifi library, to remove the compromised root.

If you maintain software that bundles root certificates, audit your dependency chain and replace the eMudhra root with a fresh, securely generated authority. For researchers, the episode demonstrates the value of automated corpus testing like paranoid_crypto for early detection of weak CAs. In environments where devices cannot be updated, consider network‑level mitigation such as a trusted proxy that validates traffic against a known‑good set of roots.

TakeawayNever assume a trusted CA remains safe; regularly update and audit all bundled root certificates.