Weak eMudhra Certificate Keys Prompt Browser Blocks and Enterprise Checks

| 2 Min Read
Browsers blocked eight eMudhra intermediates after researchers recovered weak private keys, while organizations check systems that rely on separate trust stores.

Eight eMudhra intermediate certificate authorities had private keys weak enough for researchers to recover from public certificates in less than a second. That failure could let an attacker create trusted certificates to impersonate websites or services, making browser blocks and checks of enterprise trust stores the immediate priorities.

Predictable keys exposed certificate trust

The issue came to light after a researcher identified as Wayne reported the compromise to Mozilla on October 17 at 20:06 UTC. The report had been forwarded by Google’s Chrome Root Program. Mozilla engineer Dennis Jackson said the keys could enable impersonation of any website or service.

Mozilla independently recovered the keys at 21:48 UTC, without knowing how the original reporter had obtained them. Jackson said that confirmed the key generation process was flawed and “trivial to exploit.” Security researcher Scott Helme later reported that one key was the number 4, while two others were 56 and 115. He recovered all eight from the public certificates in under a second.

Six affected intermediates were intended for Transport Layer Security (TLS), which applications use to authenticate websites and establish encrypted connections. The remaining two were for code signing. Google attributed the weakness to insufficient randomness: anyone with the private keys could forge trusted HTTPS certificates for clients that still trusted the affected authorities.

Browser protections arrived through trust updates

Google added the affected intermediates to Chrome’s Revocation List Set, blocking certificates that shared those keys without requiring users to update or restart the browser. Google Play Services delivered equivalent protections to Android devices and Chromebooks.

Google said it found no TLS certificates chaining to the six affected intermediates in Certificate Transparency logs before the block. It added that Chrome’s default enforcement of Certificate Transparency would have prevented fraudulent certificates from those authorities from being used against its clients.

Mozilla distributed a OneCRL block to Firefox users with standard configurations and announced updates for people whose custom settings might have stopped them receiving it. Google also removed the emSign ECC Root CA – G3, which signed the intermediates, from the Chrome Root Store. The change was scheduled to reach devices using that store on October 27.

Those browser measures reduce exposure for standard configurations, but organizations often have clients that rely on their own certificate stores. Yash Kadakia, founder and CTO of Security Brigade, estimated that about 30,000 legitimate certificates would need to be migrated. He warned that government and public-sector sites using the affected hierarchy could see browser warnings or access disruptions if replacement certificates were late.

Enterprise systems need their own trust checks

Kadakia urged security teams to review payment gateways, vendor integrations, older Java applications, mobile apps and network appliances. These systems may trust certificates through stores that browser revocation updates don’t cover.

Teams should identify both the certificates their services present and the certificate authorities their applications accept, then test whether affected clients reject certificates signed by the compromised keys. Kadakia also called for checks of cross-signed certificate chains.

Cloudflare said it learned of the compromise on October 19 and deployed mitigations across its content delivery network, developer services and Zero Trust products. It updated shared trust stores and base images, and issued updates for Cloudflare One clients and Cloudflare Tunnel. The company said its review had found no active exploitation on Cloudflare services.

eMudhra says the intermediates issued no certificates

In its incident statement, eMudhra said the affected intermediates were created during a key-generation ceremony in April 2025. The company said its root CA private keys and other intermediate authorities were unaffected.

“None of these intermediate CAs, including the one deployed in production, have issued any end-entity certificates,” eMudhra said, adding that public Certificate Transparency records supported its internal analysis. It said it was investigating and reviewing its security controls.

The lack of issued end-entity certificates limits evidence of exposure through normal issuance, but it doesn’t neutralize the compromised keys: someone holding one could create a fraudulent certificate without asking eMudhra. The practical next step for organizations is to verify that every relevant client and service now rejects certificates chaining to the affected authorities.

Source: Thomas Jones · www.csoonline.com

Comments

Please sign in to comment.