Tiny 3-bit keys in eMudhra TLS certs drive exit from certificate authority business

eMudhra has announced it will cease operations in the TLS certificate sector after researchers discovered that eight of its intermediate credentials contained private keys so weak they could be trivially reversed. This flaw allowed attackers to generate valid, trusted certificates for any domain.

Root cause

According to Ars Technica, the issue stemmed from a flubbed key signing ceremony that allowed the minting of web credentials for any site. The eight compromised certificates utilized NIST P-384 elliptic curve cryptography but possessed private keys with only three to eight bits of entropy. Standard keys of this type should contain roughly 384 bits, offering a vast number of possible combinations.

Attack path

An attacker could discover the correct private key for any of the eight defective intermediates in milliseconds. Once the key was known, the attacker could sign new TLS certificates for any website, email server, or device. These forged credentials would be accepted as valid by major browsers and numerous other systems that trust eMudhra’s root certificates.

Affected versions

The issue affected eight specific intermediate TLS certificates issued by eMudhra. The private keys for these credentials were the integers 4, 56, 66, 115, 155, 156, 230, and 237. These values are drastically smaller than the required security standard, rendering the cryptographic protection non-existent for any service relying on these intermediates.

Mitigation

Browser vendors blocked certificates issued using the compromised intermediate credentials within a day or two of the discovery. eMudhra stated that it is withdrawing from the global SSL/TLS business entirely. The company provided a brief explanation for the debacle on Wednesday, citing compliance costs and low revenue as factors in the decision.

Why it matters

Certificate authorities act as trusted third parties that verify the identity of websites and services. When an authority issues credentials with weak cryptographic keys, it undermines the entire chain of trust. Teams usually monitor for newly revoked certificates and ensure their validation libraries are updated. In such events, verifying that your systems rely on current root stores helps prevent acceptance of forged credentials.

What to do and how to stay safe: eMudhra

• Check your internal certificate stores to ensure the eight defective eMudhra intermediate certificates are not present or trusted.
• Monitor browser and server logs for any unexpected certificate errors or connections that may have used these weak credentials before the block.
• Verify that your automated renewal systems are not attempting to use eMudhra as a provider for new TLS certificates.
• Review your root certificate trust store configuration to confirm it aligns with the latest vendor recommendations regarding eMudhra.

Step-by-step guide: Password Policies Examples That Reduce Password Fatigue

General security guidance from the Vector Bulletin newsroom. It is not confirmed advice from the organisations named in this story.

Frequently asked questions

Did eMudhra release a fix for the weak keys?

The source material does not state that a fix or replacement certificate was issued; instead, the company announced it is exiting the TLS certificate business entirely.

How weak were the private keys found in the certificates?

The private keys ranged from just three to eight bits, with one key having a value of only four.

Why is eMudhra leaving the TLS business?

The chairman cited high compliance costs, low revenue from the sector, and the availability of free certificate providers.