Heartbleed is the name of a critical vulnerability in the OpenSSL cryptography library. In 2014, it was exploited on a large scale. The exploits allow many unaffiliated hackers to decrypt TLS-protected exchanges between parties. They also recovered private TLS certificate keys, session cookies and passwords. The attacks compromised thousands of servers, some belonging to large companies and government agencies around the world.
Recovery required a long series of steps that took years. The steps included patching OpenSSL on all affected devices, reissuing millions of TLS keys, revoking old certificates, rotating passwords and session tokens, and updating forgotten embedded devices and other systems, which was extremely time and resource intensive, especially on an Internet scale.
“Anytime you need many different people in different contexts to do something, it will take a long time,” Valsorda explained. “This time it’s worse because there are more contexts, more people and more heterogeneity.”
The compromised eMudhra keys were defective to a level that defies the imagination of many engineers studying the incident. A normal size for a NIST P-384 elliptic curve cryptography private key contains approximately 384 bits of entropy, a size allowing nearly 2384or a 116-digit number, different possibilities. The private key size of the compromised keys ranged from 3 to 8 bits. Surprisingly, the private keys were 4, 56, 66, 115, 155, 156, 230, 237.
“This falls very much into the ‘this shouldn’t be possible’ category,” Valdorda said. “Maybe some horribly dangerous key generation interface has a ‘size’ parameter and set it to 1 by mistake???”
Ben Cartwright-Cox, director of BGP.tools, said: “I’m guessing this is an example of code that accidentally leaked into production, but it’s hard to know. But it’s crazy that no one noticed.”
Gn tech
