eMudhra blames buggy script for weak certificates before quitting TLS certification
- Severity
- High
- Sources
- 1
What happened
eMudhra 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
- Check whether any certificates in use were issued by eMudhra, since browsers have stopped recognising them.
- Replace any affected eMudhra-issued certificates with ones from a trusted certificate authority.
Written by AI from the sources, checked against them