Re:Team Fortress 2 source code has leaked
by enchiridion on Wednesday April 22, 2020 @10:42PM
(#22952358)
I'm not sure if heartbleed is a good example here, given that it was basically a new class of exploit.
[ Parent
| on HN ]
Re:Team Fortress 2 source code has leaked
by missblit on Wednesday April 22, 2020 @11:13PM
(#22952498)
Wasn't heartbleed a fairly typical buffer overflow?
Re:Team Fortress 2 source code has leaked
by swixmix on Thursday April 23, 2020 @12:08AM
(#22952707)
the typical buffer overflow would have been caught by OpenBSD's protective malloc.
> [...] OpenSSL adds a wrapper around malloc & free so that the library will cache memory on it's own, and not free it to the protective malloc. [...] So then a bug shows up which leaks the content of memory mishandled by that layer. [...]
Re:Team Fortress 2 source code has leaked
by sgillen on Thursday April 23, 2020 @05:41PM
(#22961840)
I don’t think the vulnerability was in malloced memory, it was some buffer on the stack. I’ve actually patched OpenSSL to stop heart bleed as an excersice and iirc the fix was in fact just preventing a typical buffer overflow.
Re:Team Fortress 2 source code has leaked
by selestify on Thursday April 23, 2020 @12:41AM
(#22952863)
Seems like that commenter is also saying that it would’ve been caught as a regular buffer overflow bug?
> OpenSSL is not developed by a responsible team.
Re:Team Fortress 2 source code has leaked
by enchiridion on Thursday April 23, 2020 @12:41AM
(#22952865)
I've always thought of buffer overflow as writing beyond the intended bounds of the buffer.
Heartbleed is reading beyond the intended bounds remotely. I don't think there were similar attacks before hand, but I could be wrong. I only have a base level knowledge here.