eMudhra Quits TLS After a Key Failure That Shook Internet Trust
eMudhra Quits TLS After a Key Failure That Shook Internet Trust
The failure began on April 30, 2025, during a key-generation ceremony for eMudhra’s elliptic-curve certificate issuers. The company later said an approved test involving the transfer of keys between hardware security modules went wrong: a script created a second, weak set of keys, and similarly labelled keys were then used by mistake for certificate-signing requests.
The scale of that mistake became clear on Tuesday, when researchers disclosed eight eMudhra intermediate TLS certificates whose private keys ranged from just 3 to 8 bits of entropy — including the value 4. A proper P-384 key should have roughly 384 bits. Anyone who recovered the weak keys could have minted certificates trusted by browsers and many other systems, enabling interception attacks against targeted connections.
Browser makers and some major software projects blocked the intermediates within days, and there were no reported signs in certificate-transparency logs that the keys had been abused. But researchers warned that the browser response was only the beginning. Filippo Valsorda, a Go cryptography maintainer, called it “a massive cleanup job, bigger than Heartbleed,” pointing to the long tail of IoT devices, Docker containers, old Linux machines and software carrying their own root stores.
On Wednesday, eMudhra acknowledged both technical and human failures. It said revocation lists initially signed with the intended strong keys produced invalid signatures and were re-signed with the flawed keys; the company promised to recheck every key ceremony it had conducted.
By Thursday, the company had chosen a broader retreat. Chairman V. Srinivasan said global SSL/TLS generated only 1% of revenue while compliance costs rose and free certificates squeezed returns. eMudhra said the social-media scrutiny was “out of proportion” to TLS’s place in its business and that withdrawing was the right decision for shareholders.
That may close eMudhra’s chapter in the TLS market. It does not instantly close the exposure for embedded and unmaintained systems that may never receive the blocks browsers now enforce.
Write a comment