Monday 16 November
Global

Your region, kept on this device.

eMudhra blames buggy script for weak certificates before quitting TLS certification

Severity
High
Sources
1

attributes the weakness to a custom Python import routine that truncated ECDSA P-384 private scalars (48 bytes expected) during a 30 April 2025 ceremony, affecting sixteen subordinate CA key pairs in its B and C series after keys were moved from Utimaco HSMs towards Crypto4A HSMs. Certified public keys correspond to recoverable low-entropy private scalars, enabling impersonation and traffic interception. Browser vendors distrusted eMudhra-issued certificates, and the company is exiting the SSL/TLS CA business. No CVE identifiers are given. Defenders should check for eMudhra-issued certificates in their estate and plan replacement.

For security analysts · Written by AI from 1 source · Wrong?

What to do

  1. Check whether any certificates in use were issued by eMudhra, since browsers have stopped recognising them.
  2. Replace any affected eMudhra-issued certificates with ones from a trusted certificate authority.

Written by AI from the sources, checked against them

Full story timeline · 1 update

  1. Thu 12 NovemberDisgraced former CA eMudhra blames buggy script for hopelessly weak certificatesThe Register (Security)

Who reported · 1 outlet

The Register (Security)

Who and what is in it

Report a problem