Why “Heartbleed” is being discussed
The most recent Hacker News stories and comments contributing to this topic's mentions.
> It was caused by memory allocator returning uninitialized memory and every memory safe language I know about does not allow this in best-practice code. TBH this would have hap…
by lelanthran · Oct 22, 2026
For me, what was strange is there were no write-ups on how the vulnerability actually worked. It really does feel like a lot of people went "Claude found a bug, and Claude says…
by nemothekid · Oct 22, 2026
Huh? Heartbleed is literaly memory safety (buffer over read)
by redox99 · Oct 22, 2026
Heartbleed was a buffer overread. Sounds like a memory safety bug... is it not?
by phyzome · Oct 22, 2026
I don't really want to be in the WordPress world anymore (I still maintain a couple alas). But this isn't about PHP code, really — this is about C code (with less-than-ideal exc…
by dofm · Oct 21, 2026
I mean, this isn't a things-made-in-PHP-are-bad problem. It's a bit more a "certain C programming techniques are bad" problem. This is more like log4j, heartbleed etc. Won't be…
by dofm · Oct 21, 2026
Interest
Proportion of Hacker News items mentioning "heartbleed" over time.
Mentions
Total number of Hacker News items mentioning "heartbleed" over time.
Heartbleed is a security bug in some outdated versions of the OpenSSL cryptography library, which is a widely used implementation of the Transport Layer Security (TLS) protocol. It was introduced into the software in 2012 and publicly disclosed in April 2014. Heartbleed could be exploited regardless of whether the vulnerable OpenSSL instance is running as a TLS server or client. It resulted from improper input validation in the implementation of the TLS heartbeat extension. Thus, the bug's name derived from heartbeat. The vulnerability was classified as a buffer over-read, a situation where more data can be read than should be allowed. Read more on Wikipedia