News for hackers. Stuff that matters.
Re:Heartbleed in Rust by akerl_ on Monday February 02, 2015 @01:41PM (#8985864)
Heartbleed occurred because the size of the buffer was based on the size provided by the malicious packet, the buffer was not zeroed, and then the user-provided data was written to the buffer. If user-provided-data size was less than what you said it was, the rest of the buffer contained whatever it had previously contained.
Re:Heartbleed in Rust by MichaelGG on Monday February 02, 2015 @01:53PM (#8985959)
And since people were able to recover SSL keys, does this not mean that this buffer was used for... everything? Having a non zeroing allocator for an entire library seems rather ambitious. It's significantly worse then just having a buffer pool for, say, incoming packets or something.
Re:Heartbleed in Rust by akerl_ on Monday February 02, 2015 @02:32PM (#8986305)
Oh yes, using buffers without zeroing them is a terrible idea, and sharing those buffers among different types of things is a terrible idea.

I was specifically commenting on the fact that what the parent comment described as "terribly unlikely" is in fact what happened.

Re:Heartbleed in Rust by legulere on Monday February 02, 2015 @02:59PM (#8986517)
There was no buffer reuse like in the linked rust demonstration, but it was data from previous allocations.