eMudhra To Exit Certificate Business As Security Flaw Triggers Distrust

eMudhra plans to voluntarily wind down its global SSL/TLS certificate business. The decision followed the discovery that private keys for eight intermediate certificate authorities were weak enough to recover. Google and Mozilla then distrusted eMudhra’s certificates, severely affecting its global TLS operations. The incident also raised security and reputational concerns.

The company said it revoked the affected CAs within 14 hours. It said none had issued end-entity certificates, its infrastructure was not compromised, and no data was breached. Still, distrust of its G3 ECC root affected about 30,000 US certificates, which were moved to its G1 RSA root.

The business represented around 1% of global revenue, and eMudhra cited rising compliance costs, declining returns, and limited future prospects. Free certificates from Let’s Encrypt, planned free offerings from Cloudflare, and a shift toward 90-day certificates made the market less attractive. Customers will move to other providers free of charge.

SSL/TLS certificates are digital credentials used when a browser connects to a website. They bind a website’s identity to a public cryptographic key and support encryption between the browser and the site. This helps protect information moving across the connection and gives the browser a basis for checking whether the site is genuine.

Certificate authorities, or CAs, issue these credentials. A browser trusts selected root CAs and the intermediate CAs beneath them. When a site presents a certificate, the browser checks its signature, dates, domain information, and chain back to a trusted root. If those checks fail, the browser can show a security warning or block the connection.

The article focuses on eMudhra, a CA whose certificates were distrusted by Google and Mozilla after weak private keys were found. Although eMudhra said no affected CA had issued end-entity certificates, the distrust still disrupted customers and forced certificate transitions.

The incident involved eight intermediate certificate authority certificates. A researcher recovered their corresponding private keys because the keys had been generated with insufficient randomness. Six of the intermediates were intended for TLS, while two were intended for software signing.

The article distinguishes the affected CAs from customer certificates. eMudhra said none of the eight intermediates had issued end-entity certificates. However, distrust of the company’s G3 ECC root affected around 30,000 certificates in the US market. Those certificates were under ECC and had to be transitioned to eMudhra’s G1 RSA root.

The 30,000 figure describes certificates affected by the G3 distrust, not certificates issued by the eight weak intermediates. eMudhra said all eight intermediates were revoked. After announcing the business closure, the company began moving those customers to another provider, with transitions planned over three to four weeks.

Browser root programmes maintain trusted lists of certificate authorities. When Google or Mozilla removes trust from a CA or certificate hierarchy, browsers no longer accept certificates that depend on it as reliable. Visitors may see warnings, blocked connections, or other failures instead of reaching a website normally.

In eMudhra’s case, Google and Mozilla distrusted the G3 ECC hierarchy as a precaution after the weak-key incident. About 30,000 US certificates were affected because they were issued under ECC. eMudhra moved them to its G1 RSA root, which continued to operate and issue certificates.

Distrust does not necessarily mean every affected certificate was fraudulently used. eMudhra said none of the eight intermediates had issued end-entity certificates, its infrastructure remained uncompromised, and no data was breached. Even so, the browser decision created operational disruption and contributed to eMudhra’s decision to exit the global business.

A private key is meant to remain secret and is used to prove control over a certificate. Its security depends partly on strong randomness during generation. If the random values are too predictable, an attacker may be able to reconstruct the private key instead of guessing an effectively impossible secret.

With a recovered intermediate CA private key, someone could potentially sign fraudulent certificates beneath that CA. Those certificates might impersonate websites or support unauthorized software signing. Browsers and systems could trust them because they appear to come through a recognized certificate chain. The article says the eight affected keys were vulnerable to reconstruction.

The risk was serious even though eMudhra said none of the eight intermediates had issued end-entity certificates. The company revoked all eight and said no data was breached. It attributed the flaw to a script error and human oversight, not hardware, and planned stronger maker-checker controls and independent reviews.

eMudhra has two root certificate hierarchies described in the article. G1 uses RSA cryptography, while G3 uses elliptic curve cryptography, or ECC. The browser response focused on G3 after the security incident involving eight intermediate CA certificates with recoverable private keys.

The distrust affected certificates issued under the G3 ECC hierarchy. About 30,000 US certificates were affected because they were under ECC, so eMudhra transitioned them to its G1 RSA root. Google and Mozilla took this step as a precaution after the weak-key discovery.

G1 continued to operate and issue certificates. The article also says all certificates in India and adjoining markets came from G1, while the G3 distrust affected an undisclosed US client. The distinction reduced the disruption’s scope, but eMudhra still decided to leave the global certificate business and move customers to alternative providers.

eMudhra’s existing customers will be moved to alternative certificate providers free of charge. The company is working with other certificate partners to avoid service disruptions. It first shifted affected US certificates from the distrusted G3 ECC root to its operating G1 RSA root, but now plans to transition those customers to another provider.

The market has become difficult because Let’s Encrypt already offers free TLS certificates, while Cloudflare plans to do the same. Browser guidelines are also moving toward 90-day certificates. Shorter certificate periods can increase operational work and reduce the appeal of selling longer-lasting certificates. These pressures limit the revenue available to commercial providers.

For eMudhra, the segment generated around 1% of global revenue. The company cited rising compliance costs, declining returns, and limited future prospects, alongside the security incident. It plans to focus on more complex customer problems, including AI and quantum computing, while completing customer transitions within three to four weeks.