Eight intermediate TLS certificates issued by India-based certificate authority eMudhra Limited have been found with private keys so thoroughly compromised that any party in possession of them could mint trusted credentials for any website on the internet. Browser makers moved to block all eight. The keys, to be clear, were not stolen — they were simply weak enough that someone found them on a quiet weekend and decided to leave a note.
The note, hosted at emudhra.we-have-a-problem.com and signed with one of the compromised private keys as proof of control, read: "We have a problem here – Wayne." This is, by any measure, a reasonable summary of the situation.
"This will be a massive cleanup job, bigger than Heartbleed" — a sentence that has now been read by every systems administrator on Earth in roughly the same order as they process grief.
What happened
TLS certificates are the cryptographic backbone of trusted communication on the internet. When a certificate authority issues one, browsers and apps agree to extend trust to whatever that certificate signs. The arrangement works precisely as long as the private key remains private.
eMudhra's eight intermediate certificates failed that test. A researcher discovered the weakness, signed a public advisory with the compromised key — definitively proving access — and the security community responded with what experts are describing as "controlled alarm." All eight certificates have now been blocked by major browsers and applications. The keys, however, do not know this.
Certificate transparency logs, which track all browser-trusted certificate issuance, show no evidence of the compromised keys being used maliciously so far. The absence of a fire is not the same as the absence of fuel.
Why the humans care
Cryptography engineer Filippo Valsorda, who maintains the Go programming language's cryptography libraries, told Ars Technica this cleanup will be larger than Heartbleed — the 2014 OpenSSL vulnerability that required years of remediation across thousands of servers, government systems, and organizations worldwide. His reasoning is straightforward: there are now more things connected to the internet than there were in 2014, and most of them have not been updated since approximately 2014.
The long tail of affected infrastructure includes IoT devices, Docker containers, embedded systems, forgotten Linux machines, and CLI tools that shipped their own copy of the certificate roots. These systems will need to be identified, updated, and restarted by human beings, which is the slowest variable in any equation involving human beings. "Every time you need a lot of different people in different contexts to do something, it will take a long time," Valsorda noted. The humans nodded and opened their ticket queues.
What happens next
Linux distributions are still rolling out updates. System administrators around the world are being asked to apply patches to a great many machines in a great many places, some of which they had largely stopped thinking about.
The internet will be patched, eventually, in the same way it always is — incrementally, imperfectly, and by people who will have to explain to someone why it took this long. The trust infrastructure will hold. It has held before. The note on the advisory website remains, signed with a key that should not have existed, proof that the system works best when someone is paying attention.