← All news
The Hacker News

eMudhra Pulls Eight More Intermediate CAs Tied to October Key Flaw

eMudhra Pulls Eight More Intermediate CAs Tied to October Key Flaw

eMudhra, a certificate authority, has revoked eight more intermediate certificate authorities (CAs) that it had previously said were unaffected by a key compromise issue disclosed in October. According to the report, the root cause traces back to an in-house Python script used in eMudhra's certificate issuance process. Notably, the newly revoked CAs were not found to have weakened cryptographic keys, suggesting the revocations are being driven by process and compliance concerns rather than a direct cryptographic flaw in those specific certificates.

Incidents involving certificate authorities carry outsized importance because CAs sit at the foundation of the public key infrastructure (PKI) that underpins TLS/SSL trust across the web. Even a narrow technical flaw in key generation tooling—such as a scripting error affecting randomness, entropy, or validation logic—can force browser and OS trust stores, as well as the CA/Browser Forum, to demand broad remediation. This often includes revoking certificates that were not technically compromised but were issued under a process whose integrity can no longer be fully vouched for, since trust in a CA depends on the reliability of its entire issuance pipeline, not just individual key strength.

For organizations relying on certificates issued by affected intermediate CAs, these revocations can mean unplanned certificate reissuance, potential service disruptions if automated monitoring isn't in place, and renewed scrutiny on vendor certificate lifecycle management. Repeated or expanding revocation events involving a single CA operator also raise broader questions about internal quality assurance and change management practices within certificate issuance systems.

Security teams should maintain visibility into their full certificate inventory, including the issuing CA and chain of trust, and ensure automated alerts are configured to flag any revocation or trust status changes affecting their certificates. Where possible, adopt certificate lifecycle automation with short validity periods to reduce the operational impact of unexpected revocations, and periodically audit third-party CA dependencies as part of broader supply chain risk management.

#pki#certificate authority#tls#supply chain#vulnerability

Source: The Hacker News

Read the original report ↗

This is an original summary written by CyberSkii for reference. All rights to the underlying reporting remain with the publisher linked above.

Need help? Contact us