Eight intermediate TLS certificates from India-based certificate authority eMudhra Limited had private keys so weak that anyone could use them to mint browser-trusted credentials for any site on the Internet.
An intermediate certificate is a credential a certificate authority uses to sign the certificates that websites present to browsers. Whoever holds its private key can issue certificates that millions of servers and devices will accept as genuine. Here, the keys were weak enough that outsiders could get at them.
An informal advisory appeared over the weekend at emudhra.we-have-a-problem.com. It carried the message "We have a problem here - Wayne," digitally signed with the private key of one of the eMudhra certificates. That signature was the proof: whoever posted it controlled a key that could also sign unauthorized certificates. Security teams around the world went on high alert Tuesday.
The response has been quick where updates are easy. By late morning Tuesday, browser makers and some major apps and programming languages had blocked all eight certificates. Certificate transparency logs, the public records of every browser-trusted certificate issued, show no reports of the compromised keys being used maliciously.
The harder part is the long tail. Linux distributions and embedded and Internet-of-things devices carry their own lists of trusted certificates, and updating them will be hard and time-consuming, according to the reporting. Until that happens, those systems still trust certificates that nobody should.
The closest precedent is DigiNotar, the Dutch authority breached in 2011 and removed from browser trust. The difference here is the evidence so far: a signed message and clean transparency logs, not forged certificates in circulation. That leaves defenders a window, and the speed of browser blocks suggests the fast-updating parts of the ecosystem are already covered. The exposure now sits with the devices that update slowly, and those are the ones an attacker would pick.