Eight eMudhra Intermediate CA Private Keys Compromised by Weak Randomness
Summary
Unit 42 reports that weak randomness compromised eight eMudhra intermediate CA private keys, potentially enabling unauthorized TLS certificates and MitM attacks. eMudhra revoked the certificates, and browser and OS vendors moved to distrust them.
Key points
- Unit 42 says insufficient randomness during certificate generation compromised eight eMudhra intermediate CA private keys, potentially allowing derivation from public certificates.
- Derived keys could be used to sign unauthorized public TLS certificates and enable traffic interception, impersonation, or session hijacking.
- eMudhra revoked the eight certificates; major browser and operating-system vendors moved to revoke or distrust the affected intermediates.
- Organizations are advised to identify certificates chaining to the affected CAs and check applications, build pipelines, and custom trust stores for embedded eMudhra certificates.
- Reissue affected certificates through another trusted CA, update trust stores, and enforce CRL and OCSP revocation checks.
- Review network, proxy, DNS, authentication, and identity logs for signs of suspicious certificate use or possible interception.
- For longer-term protection, monitor Certificate Transparency logs, restrict issuers with CAA records, and harden certificate lifecycle management.
Article Details
- Defense Focus
- Detect and contain risks from compromised eMudhra intermediate CA private keys, including unauthorized certificate use and potential MitM activity.
- Detection Methods
- Inventory public-facing and internal services and identify certificates chaining to the affected eMudhra intermediate CAs.
- Search network, proxy, and DNS logs for anomalous connections to unknown external IPs using eMudhra-signed certificates.
- Monitor for unexplained increases in TLS handshake failures, certificate validation errors, and untrusted-issuer warnings.
- Review authentication and identity logs for sensitive-service access around the compromise timeframe and possible session interception or replay.
- Monitor Certificate Transparency logs for unauthorized certificates issued for organizational domains.
- Data Sources
- PKI asset and certificate inventories
- Network egress, proxy, and DNS logs
- TLS handshake and certificate-validation telemetry
- Authentication and identity logs
- Public Certificate Transparency logs
- Code repositories, build pipelines, and custom trust stores
- Defensive Actions
- Revoke and reissue certificates chaining to the compromised intermediates through an alternative trusted CA.
- Deploy updated trust stores that explicitly distrust or revoke the affected intermediates.
- Enforce CRL and OCSP checks on proxies, API gateways, egress controls, and security appliances.
- Audit repositories, build pipelines, containers, and runtime trust stores for bundled eMudhra certificates or trust anchors.
- Add or update DNS CAA records to restrict authorized certificate issuers.
- Harden automated certificate lifecycle management and use short-lived certificates where feasible.
Vendors
eMudhraEight intermediate certificate authority (CA) private keys belonging to Indian CA eMudhra Limited were compromised due to a critical cryptographic defect during the certificate generation process.Palo Alto NetworksPalo Alto Networks is designed to assist customers with managing certificate lifecycles through its Palo Alto Networks Next-Gen Trust Security solution.
Products
Next-Gen Trust SecurityPalo Alto Networks is designed to assist customers with managing certificate lifecycles through its Palo Alto Networks Next-Gen Trust Security solution.Strata Cloud ManagerBy integrating discovery and automation into Strata Cloud Manager, NGTS provides the cryptographic agility needed to manage compressing 47-day lifecycles and respond to emergency events with automated reissuance and