eMudhra Issues Certificates With Trivially Guessable Keys, Threatening Global Device Security
Eight intermediate certificates containing one-byte private keys were distributed by an Indian certificate authority, requiring widespread updates across countless devices and applications to prevent impersonation attacks.
By Thomas Reynolds ·
A routine week for systems administrators has turned critical as a security flaw in issued certificates threatens to compromise the integrity of billions of devices worldwide.
The issue centers on eight intermediate certificates released by the Indian certificate authority eMudhra. Six of these are designated for TLS traffic, while the remaining two are intended for code signing. The private keys associated with these certificates were generated with only one byte of entropy, meaning they consist of a number between 0 and 255. This extremely low complexity renders the keys trivial for an attacker to brute-force in a fraction of a second. The specific cause of this generation failure remains under investigation.
The danger arises because software verifies the legitimacy of a website by validating a chain of trust. This chain typically begins with a root certificate, whose keys are stored securely offline, and passes through intermediate certification authorities that issue specific certificates. In this instance, the intermediate keys can be easily derived, allowing an attacker positioned anywhere on a network path—such as a public Wi-Fi hotspot or an internet service provider—to intercept traffic and impersonate high-profile domains, including major banking or technology sites. Furthermore, regarding the code signing certificates, a malicious application could be presented to a user as a legitimate program signed by a trusted vendor.
To mitigate this, operating systems and applications must update their lists of trusted certificates to revoke the eight affected keys or reject the corresponding root certificate. However, recent versions of Chrome, Brave, Firefox, and Safari utilize a mechanism called Certificate Transparency. This feature consults a public log of certificate issuances and blocks any unlisted certificates. Google reports that no certificates signed by the six affected TLS intermediate CAs were logged, suggesting that standard web browsing is currently protected on these modern browsers. Despite this safeguard, the requirement to update software remains urgent for other applications.
The scope of the necessary remediation is vast, encompassing nearly every category of computing device and software. Servers, operating systems, phones, tablets, and routers all require updates, as do virtual machines and containers such as Docker. Programming languages including Python, Go, Node.js, and Rust, along with standalone download utilities like curl, must also be patched to ensure they reject the compromised keys. While major platforms are expected to release fixes promptly, older routers, smart home devices, and legacy computers present a significant challenge. These older devices may never receive the necessary updates, potentially leaving them permanently vulnerable to impersonation attacks.
The situation has escalated following a critical PHP remote code execution vulnerability that administrators were already handling. Now, the widespread requirement to revoke or reject these eight certificates adds a substantial burden to IT operations. Because the private keys are so easily compromised, any device or application that has not been updated remains susceptible to interception. Users are advised to check for and apply updates across all installed software and network equipment immediately to secure their systems against potential impersonation.
Source: Tom's Hardware
