Press "Enter" to skip to content

eMudhra Details Python Bug Behind Weak Security Keys

Indian cybersecurity firm eMudhra has published a detailed report on the incident that exposed eight weak security keys and triggered a brief internet‑wide alert last month. The report, posted on the open‑source bug‑tracking platform Bugzilla, attributes the vulnerability to a coding mistake in a custom Python script used during a key‑generation ceremony on 30 April 2025.

How the weak keys were created

eMudhra operates as a certificate authority (CA), issuing digital certificates that enable browsers to display the padlock icon indicating a secure connection. According to the company’s own findings, the affected keys were meant to be 115 digits long, a length that normally provides strong cryptographic protection. Instead, a programming error reduced eight of the keys to single‑ or low‑digit numbers. The values identified in the report were 4, 56, 66, 115, 155, 156, 230 and 237, with the most extreme case being the solitary digit “4”.

The keys were generated successfully on a hardware security module (HSM) during a ceremony on 30 April 2025. After generation, a custom Python script prepared the keys for transfer to a different HSM located in another geography. A bug in that script unintentionally truncated the keys, shrinking them to the tiny numbers later discovered. The report notes that this was the first occasion eMudhra employed such a cross‑geolocation transfer process.

Impact and discovery

Because the truncated keys still functioned within the CA’s infrastructure, they continued to issue certificates for eighteen months without raising alarms. The company acknowledges that the keys were never subjected to strength testing during that period, allowing the weak values to remain in active use. In parallel, eight additional keys remained intact, but copies of those keys were inadvertently stored in the memory of an ordinary computer, further widening the exposure.

When the weakness became public, security experts warned that the compromised keys could have enabled malicious actors to obtain legitimate certificates and create counterfeit websites, potentially facilitating phishing or other scams. Some commentators even suggested that the flaw had the theoretical capacity to “break the internet.”

Response from the ecosystem and eMudhra’s remediation

Following the public disclosure, major browser vendors and operating‑system providers—including Google, Mozilla, Apple and Microsoft—issued rapid security updates to mitigate any risk posed by the compromised certificates. eMudhra responded by revoking all sixteen certificates associated with the eight weakened keys and the eight copies stored in ordinary memory, stating that it could not guarantee compliance with its own security policy for those certificates.

In the aftermath, eMudhra announced that it would exit the digital certificate business entirely, ending its role as a CA. The company issued a public apology for the incident and indicated that it has since abandoned the practice of transferring keys between HSMs. Future key generation will be performed without cross‑device movement, eliminating the scripting step that caused the original fault.

Overall, the incident underscores the critical importance of rigorous testing and validation in cryptographic operations. While the immediate threat was contained through coordinated updates and revocations, the episode serves as a cautionary tale for other certificate authorities and organizations that rely on automated scripts for key management.

Be First to Comment

Leave a Reply

Your email address will not be published. Required fields are marked *