“Lemmeme” tho. 'twas RIGHT there.
An organization trusted with the security of potentially billions of people essentially used the password “4” among other bad choices.
You can read the technical explanation here: https://emudhra.we-have-a-problem.com/
There are two parts to this answer.
First, as many have pointed out, eMudhra as a trusted certificate authority has issued eight high-level certificates with a key length of onle 3-8 bits, when they should be 384 bits long. And yes, the smallest key was ‘4’.
But the other point is tha xkcd predicted using 4 as a random number, decades ago. It was supposed to be a joke.
supposed to …
xkcd also happened to release a comic about a “vulnerability in the number 3” the same day the eMudhra news broke.
Check the alt text on that one :-)
That’s not “happened to”; read the title text if you want to remove all reasonable doubt that it’s a reference to it.
I think they italcized that word because it was sardonic.
Oh my god, I thought that was a recent meme someone made because of this debacle, didn’t know it was an OG xkcd…
It’s hard to properly describe how big a fuckup this is. All I will say is that all the coverage I’ve seen is underselling the potential for harm. There’s nothing you can do except update your shit, pray that everyone in the upstream supply chain of every service you use has updated their shit, and take comfort in the fact that there are no proven wild exploits out there (yet).
Well, even if there’s no update for your shit, it’s still possible to go into the certificate store your browser/OS/whatever uses and delete the compromised certificates.
Not much you can do about everyone else not updating their shit though.
I tried to read the comments, but I couldn’t get in:
In my defense, the comm is No Stupid Questions, not No Stupid Comments.
There is a massive security incident this week where an Indian certificate authority used 4 as the private key they used to sign encrypted internet traffic with.
Knowing their secret key lets anyone forge certificates that they can use to snoop on or modify internet traffic.
All 8 of their private keys were under 255, so could be trivially guessed. These certificates were accepted by all major browsers and operating systems, as well as many programming languages and tools.
Nit: That that key doesn’t technically encrypt traffic, if I understand correctly. It’s used to verify the identify of a website. So someone with this private key can’t directly read internet traffic. They can set up a man-in-the-middle attack, but they’d also have to compromise DNS to pull it off.
Yes, I think you’re correct
I just dont understand why they would do this? Putting so shitty key is like they wanted to make it as insecure as possible. Even if the ones responsible were criminally stupid, they still should have understood that this is like leaving the whole thing unlocked.
And for such critical thing. Imagine if this wasnt discovered like this but instead by some competent malicious actor that had resources to coordinate some large scale attack and kept it hidden until just the right moment when they can strike at everything.
I also dont understand how little outrage there even is about this, we were really close to huge catastrophe. Or maybe i have misunderstood the severity of what happened.
They are saying there were mistakes made with their key generation scripts:
We have done some preliminary assessment, there appears to be a flaw in the KGC script that was used on that specific day to create these ECC issuers. As for these ECC keys, our review of the KGC, assessment of the code and view of HSM keys so far indicate that a) a set of original ECC keys were created onboard as expected b) an approved deviation to our usual KGC to test a wrap/unwrap was introduced as these keys were meant for export for this instance c) a flaw in the code resulted in the second pair of keys being created onboard which were weaker d) these second pair of weaker keys were used by mistake to create the csr (because the key labels were similar) and signed by our root e) the CSR from these weaker keys were also sent over to Sectigo for cross signing (we verified the files sent over to Sectigo)
Source: https://bugzilla.mozilla.org/show_bug.cgi?id=2083449#c11
Personally I’m still a little confused why it makes any difference that the keys were intended for export to their European and US operations
Interesting question! Google spit this out and it makes sense:
The primary reason these specific keys/issuers were created was to solve data sovereignty and data residency requirements for customers in those regions.
Many European and US corporate clients operate under strict legal frameworks (like GDPR in Europe or various federal compliance standards in the US) that legally dictate where cryptographic infrastructure can live, where data can be decrypted, and who can possess the root or intermediate private keys.
Generating separate regional keys is a compliance mechanism to guarantee that a customer’s data or handshake traffic stays within their jurisdiction.
But, since nobody would expect an organization like that to have a one digit key, wouldn’t that make it extremely hard to guess?
Half kidding here.
It’s kinda like locking your door by putting a wedge in the crack. Probably, no one is going to try to open your door anyways, and probably, even if they did no one is going to take 5 seconds to examine the door and figure it out
But if someone does, it’s laughably easy to figure it out
Except this is internet and pretty much anybody on the planet could test the security of your doors.
I like the analogy but I think it doesn’t really apply when it comes to devices that are connected to the internet.
I think their analogy is still good. Just add “…and your door opens onto Times Square.”
That doesn’t quite get the full scope, but it does imply the danger pretty well. Plus, if you add in “…Times Square of robots, and the robots are all thieves, and your most expensive possession is visibly sitting right inside, and…” it starts to get pretty unwieldy.
Security by obscurity is what it’s called in the industry, and yeah it’s not a good way to do it. Automation and scripts would make it trivial to guess.
Well, someone did guess it so it’s not that hard. The entropy was really low.
‘Entropy’ doesnt apply here
It does doesn’t it?
The higher the number of bits, the more entropy in the system.
It’s a pointlessly obscure way of saying there are more numbers
Its a measure of the randomness of numbers in the system, ie the definition of entropy.
People do use it to sound cool, but this use still fits its mathematic definition.
I know. Its still pointlessly obscure
Not if you’re brute forcing it.
“Time to brute force this key, I guess I will go get some lun… What do you mean it’s already done? Who uses 4???”
Ain’t no way I’m starting from 0 if the standard key is 256-bit
It’s just as arbitrary as any other number. You can pick at random, but starting with a dictionary attack of easy, non-random keys would probably be a better start.
I remember playing a game of dvd-deal or no deal, where you would pick random number from one to twenty and see if you won money. The people I was playing with were mad because I just started guessing 1, 2, 3, 4…
I told them statistically it was just as likely to be those numbers as anything else.
I think it technically was not “brute forcing” (since it wasn’t found by searching the entire key space), but specifically someone tried generating CA cert private keys from numbers 0-255, and surprisingly found a few.
So why did it take so long for someone to try it?
We don’t know whether anyone tried it before April 2025, because that’s when the vulnerable certificates were issued. If someone did try it before then, they would not find any certificates (as expected) and probably wouldn’t even talk to anyone about it.
It feels like the kind if thing that someone, somewhere would have a script running constantly testing for private keys with low values. That it went 18 months without being found is a miracle!
I think there’s a good chance people will be looking for this now so will get caught a lot quicker next time.
I think there’s a good chance people will be looking for this now so will get caught a lot quicker next time.
That’s pretty much guaranteed from now on, yes.
It feels like the kind if thing that someone, somewhere would have a script running constantly testing for private keys with low values. That it went 18 months without being found is a miracle!
It’s not the kind of thing you’d expect to need to guard against, or even really think of. It should not happen. It sounds like someone was kind of just fooling around with making private keys and stumbled upon it.
I guess now someone needs to try seeding some of the most popular PRNGs with 0-255 and seeing whether any keys come up in the first few hundred numbers.
Kind of like how you don’t expect to walk up to an atm, press 1234, and hope for a million dollars to spit out.
You may find that answr from another community helpful: https://feddit.online/comment/10016475
That was a really good answer actually
Aw, thanks
Because it was revealed that an actual TLS certificate used the number 4 as a private key.
I’m glad I use good ol’ 12345!
Amazing. I have the same combination on my luggage.
I’m surrounded by Assholes!
Not just a tls certificate, A root CA certificate trusted by pretty much everything
because 42 would have been too obvious.
