Indian tech company eMudhra announces withdrawal from certificate business after security incident
eMudhra is exiting the global TLS certificate business after a researcher recovered eight intermediate CA private keys — one was literally the number 4 — exposing a catastrophic key-generation failure that should prompt immediate certificate inventory checks.
Summary written by editorial AI · Source link below
The issue was publicized by cybersecurity researcher Scott Helme, who published a blog saying that instead of a random 384-bit number, one of the company's private keys was just the number four.
Editorial Analysis
A certificate authority shipping guessable private keys shatters the trust model; any enterprise using eMudhra certs faces immediate TLS integrity risk.
Search certificate inventories and CT logs for eMudhra-chained certificates and replace them with certificates from a CA with audited key-generation practices.
A certificate authority's private keys were trivially guessable — enterprises must verify they hold no eMudhra-issued certificates.
Forward-looking interpretation drafted by editorial AI under human review — not a reproduction of the source. See methodology.
External link — opens at The Record in a new tab.
More from the Vulnerabilities Desk
- Unpatched Tailscale SSH Flaws Could Let a Hacked Device Reach Root on Other Servers1d
- Brotli Decoder Flaw Behind Node.js RCE Also Affects Bun, Python and Other Widely Used Software2d
- Abandoned Popcorn Time app exposed millions of devices to RCE attacks3d
- HPE patches eight max severity RCE and auth bypass AOS flaws3d
- Compromised TLS Certificates3d