Search

Cookies

We use cookies to improve your experience. By continuing, you accept our use of cookies.

Technology

eMudhra Exits Global SSL/TLS Business After 18-Month Undetected Key Flaw

· · 3 min read

eMudhra is exiting its global SSL/TLS business after a critical key-generation script error went undetected for 18 months, creating predictable private keys across several certificate authorities. The lapse raises significant concerns about the firm's internal security controls and audit processes.

eMudhra Ltd., a prominent provider of digital trust services, is discontinuing its global SSL/TLS business segment following the discovery of a severe cryptographic flaw. The incident, which involved a key-generation script error producing predictable private keys, remained undetected for approximately 18 months, prompting widespread concern over the company's security protocols.

The vulnerability, originating from an error on April 30, 2025, affected eight intermediate certificate authorities (CAs) by generating private keys that were not sufficiently random. This fundamental security breakdown went unnoticed through two separate audit cycles, raising critical questions about the effectiveness of eMudhra's internal safeguards and independent verification processes.

The Nature of the Cryptographic Flaw

A key-generation script is designed to create unique and unpredictable cryptographic keys essential for securing digital communications. In eMudhra's case, a flaw in this script led to the creation of easily guessable private keys, compromising the integrity of any certificates that might have been issued.

  • Origin: Key-generation script error on April 30, 2025.
  • Impact: Produced predictable private keys across eight intermediate CAs.
  • Duration: Remained undetected for around 18 months.
  • Audit Failure: Missed through two independent audit cycles.

While seven of the affected intermediate CAs were never deployed in production, and the eighth, though deployed, issued zero end-entity certificates, the underlying lapse points to a significant control failure. eMudhra co-founder Kaushik Srinivasan described the event as a "process lapse, human oversight and a script error that should have been caught by adequate controls." He affirmed that no data breach or infrastructure compromise occurred, and the company's core Indian digital signature certificate (DSC) and eSign businesses remain unaffected.

Industry Scrutiny and Future Implications

Industry experts have highlighted the seriousness of eMudhra's security lapse. Murali Rao, Cyber Consulting Leader at EY, emphasized the foundational role of certificate authorities in digital trust. "Weak private keys remaining undetected through two audit cycles raise serious questions about what those audits actually verified," Rao stated. He stressed the importance of audits verifying actual cryptographic keys rather than just procedural documentation.

Rao also pointed to a broader cybersecurity challenge: asset visibility. "If you don’t know what you have, it is impossible to defend or secure," he noted, underscoring the difficulties companies face in tracking TLS certificates, software versions, and cryptographic secrets across their infrastructure.

eMudhra's exit from the global SSL/TLS market, a segment contributing approximately 1% of its revenue, will allow it to concentrate on enterprise solutions and other trust services. However, merely withdrawing from the market does not resolve the underlying security deficiencies. To regain trust, eMudhra must:

  1. Publish transparent technical findings regarding the incident.
  2. Offer independent proof that its other operations are secure.
  3. Demonstrate that its key-generation processes have been rigorously hardened for its domestic market operations.

This incident serves as a stark reminder for all organizations about the critical need for robust, independently verified security controls, especially within infrastructure vital to digital trust.

Related