Guess what? eMudhra, a certificate authority (CA) you probably didn't think much about, has been caught with its pants down. Among its "private keys," we have the impressive numbers: 4, 56, and 115. Yes, you read that right. Just numbers. I managed to find these on my laptop in less time than it takes to brew a cup of coffee.
What Actually Happened
On the oh-so-exciting date of October 17th, a security researcher Scott Helme alerted Apple, Google, Microsoft, Mozilla, and eMudhra that private keys for eight of eMudhra's intermediate certificates had been compromised. It took about half a heartbeat for Chrome to push an update to block these certificates that very evening, and Mozilla followed suit hours later. The announcement went public on October 20th. Who needs suspense when you have instant disaster response?
These eight intermediates consisted of six TLS issuing CAs and two code-signing CAs, all created in the golden age of April 2025. But, wait! They were all cross-signed by Sectigo's “AAA Certificate Services” in May 2025. Why not throw in a few more layers of confusion?
The Fun Part: How This Happened
Now here's where it gets spicy. According to Ian Carroll, the keys are "inherently weak single-byte keys that anyone can factor." You know, typical CA stuff.
These keys are elliptic-curve keys on the P-384 curve. A real private key should be a hefty 384-bit number with roughly 10¹¹⁵ possibilities. But eMudhra's keys? They look like this:
d = 0x000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000004
That's right, it’s just a single byte with a variety of thrilling possibilities. A P-384 private key should have a more complex, interesting representation, but eMudhra decided to go minimalist instead. Their entire security scheme hinged on eight bits. Bravo!
The Great Escape for Hackers
Theoretically, if someone wanted to exploit these keys, they'd just need to do some basic math. Compute 1 × G, 2 × G, up to 255 × G, and voilà! The whole thing's compromised. And no one even had to steal a thing. The keys were essentially on sale from day one—clearance pricing on the dark web, if you will.
Who’s in Trouble Now?
If you're using a mainstream and updated browser like Chrome or Firefox, you're probably safe. But if you have any non-browser TLS clients—like curl, Node, or your favorite IoT device—you might be in trouble. These lovely pieces of tech don’t bother checking for certificate revocation by default, which is just a delightful excuse for chaos.
What to Do?
Time to play catch-up! Here are a couple of steps you can take to defend your digital kingdom:
- Update everything: Make sure to update your OS, packages, and anything else with a CA bundle. Seriously, don't skip this step.
- Devices you Can't Update: The ones you can't easily patch? Those are the true headache. Many will cling to these certificates until 2039. Good luck with that!
So, in summary, eMudhra's entire security infrastructure was riding on eight bits for 17 whole months. Just think of all the wonderful chaos that could’ve happened. What a way to keep things interesting in the world of cybersecurity!
