
On 7 April 2014 the OpenSSL project announced a vulnerability that quickly acquired a name and a logo: Heartbleed (CVE-2014-0160). It affected one of the most widely used encryption libraries on the internet, and it became a turning point in how the industry thinks about open-source infrastructure and vulnerability response.
What went wrong
OpenSSL supported a TLS feature called the heartbeat extension, which lets one side of a connection check that the other is still there by sending a small message and asking for it back. The code trusted the length field supplied by the sender without checking it against the actual message. A request could claim to be much longer than it was, and the server would answer with up to 64 kilobytes of whatever happened to be in its memory next to the message.
That memory could contain session cookies, passwords and, in some circumstances, the server's private key. Requests left little trace in normal logs. The flaw was present in OpenSSL 1.0.1 through 1.0.1f, released over roughly two years, and was fixed in version 1.0.1g. It was found independently by a researcher at Google and by engineers at the Finnish security company Codenomicon.
The clean-up
Patching the library was only the first step. Because private keys might have leaked, careful operators also replaced their TLS certificates, revoked the old ones and asked users to change passwords once the fix was in place. Many organisations discovered that they did not know where OpenSSL was running: in appliances, embedded devices and forgotten servers. Some vulnerable systems remained online for years.
Lessons for defenders
- Know your components. A software inventory, today often in the form of a software bill of materials (SBOM), turns "are we affected?" from a week of searching into a query.
- Plan for key compromise. Certificate and key rotation should be a routine procedure, not an emergency improvisation.
- Look for exploitation, not just exposure. Network sensors that recorded traffic could later check whether malicious heartbeat requests had been received.
- Fund the foundations. Heartbleed showed how few people maintained critical code. The Linux Foundation launched its Core Infrastructure Initiative weeks later, and later efforts such as the Open Source Security Foundation continue that work.
Everyone was affected
Banks, email providers, government portals, online shops, betting sites and casino platforms all scrambled to patch and reissue certificates that April. Any service that handles logins and payments over TLS had the same exposure, and the same need to tell customers clearly what had happened and what to do. The organisations that coped best were those that already knew what software they ran and had rehearsed replacing keys.