Leaked Keys Let Hackers Spoof Any Website

Systems administrators across the country are dealing with a new security headache this week. It follows immediately after they spent their time patching a critical PHP vulnerability. Now, they must rush to update countless machines and software applications. The cause is a set of eight insecure intermediate certificates. These flaws allow attackers to impersonate any domain or make malware appear legitimate.

The risk is significant for anyone sending data over a network. An attacker positioned in the path of your traffic could intercept your connection. This might happen on a public Wi-Fi network, within a corporate or government intranet, or even at the level of your internet service provider. With the compromised certificates, a hacker could pretend to be major sites like Apple, Amazon, or Bank of America. Your operating system and installed software would likely accept the connection as safe if they have not been updated.

The issue also extends to code signing certificates. This means an application you download could be flagged as coming from a trusted source, such as Microsoft or Google. In reality, it could be malicious software. Software verifies legitimacy by checking a chain of trust. A website certificate is signed by an intermediate Certification Authority. That authority is then trusted by root certificates, which are kept in secure offline storage. This week, an Indian firm named eMudhra issued six TLS certificates and two code-signing certificates with weak keys.

The technical flaw is quite simple to exploit. Private keys are the secret half of a certificate pair. For some reason, the keys for these eight certificates were only one byte long. This limits the possible values to a number between zero and 255. An attacker can guess the correct number in a split second. It is still under investigation how such a short key was generated and issued.

To fix the problem, operating systems and applications must update their trust lists. They need to revoke the eight affected certificates or remove the specific root certificate involved. Some systems may instead hard-code a rejection of the affected keys. Browsers maintain revocation lists to mark certificates as untrusted. These lists are updated regularly when errors occur. Users should check for updates to ensure their devices have the latest lists.

There is some good news for regular web users. Modern versions of Chrome, Brave, Firefox, and Safari use a feature called Certificate Transparency. This feature checks a public log of all issued certificates. It blocks any certificate that is not listed in that log. Google reports that no certificates signed by the six affected intermediate authorities were logged. If you only browse the web, you are likely safe. However, you should still update your software.

The scale of the update requirement is massive. It includes personal computers, servers, phones, tablets, and routers. It also covers web browsers, virtual machines, and containers. Programming languages like Python, Go, Node.js, and Rust are also affected. Standalone tools like curl need patches as well. Older devices, such as smart appliances and legacy computers, may present a longer-term problem if they do not receive updates.

The sheer number of categories affected makes this a complex task. From desktop operating systems to embedded systems in home appliances, the list is long. It includes web browsers wrapped inside apps and various virtual server environments. While the immediate threat to modern web browsers is lower due to transparency logs, the broader ecosystem requires attention. Users should prioritize updating their primary systems and check for patches on their mobile devices and routers.