HNHacker News
TopNewBestAskShowJobs

chrisrohlf

75 karma · joined March 29, 2012

Security stuff, C/C++, other stuff

https://struct.github.io https://secure.dev

submissionscomments
chrisrohlf··on My heart is ok, but my eyes are bleeding
There have been remote code execution vulnerabilities in OpenSSL in the past, yet no one panicked. Those vulnerabilities gave you what heartbleed does and more. The worst part about heartbleed is that its easy to exploit and the tools to do it are readily available. Its bad, as I state, but not the end of the world. The main point of the post was to correct the public analysis of the freelist implementation.

Please don't mistake a poor attempt at humor for ego.

chrisrohlf··on My heart is ok, but my eyes are bleeding
Yes, it was.
chrisrohlf··on My heart is ok, but my eyes are bleeding
Agree with most of this except for "and many specialized allocators have their own security mitigation build in." This is generally not true in my experience [1] when it comes to unlink checks, guard pages and the like. Often a generic homegrown allocator will call mmap/VirtualAlloc and chunk the page(s) up into a doubly linked list or simple arena allocator.

Sometimes a default generic allocator will have design properties about it that make exploiting certain bug classes difficult (e.g. WebKits RenderArena and Use-After-Free). There are exceptions of course, see Chromes Partition Alloc for one example.

Heap hardening/exploit mitigations are hard to get right. Ptmalloc has done a decent job save for 1 or 2 techniques lost to time. As a result modern exploits target application specific data (C++ object vtables, function pointers, etc) and not heap meta data.

[1] I wrote this blog post and I audit code for a living

chrisrohlf··on GCC Poison
gets is not missing from the list. As for alloca() please see http://blog.exodusintel.com/2013/01/07/who-was-phone/ as an example of how things can go very wrong. memcpy() isn't bad in itself but its easy to get wrong when you're dealing with untrusted user supplied size parameters. memcpy_s is a better alternative because it encourages the developer to think about the size parameters being passed in.
chrisrohlf··on GCC Poison
Hi. I wrote this post and I agree with you about this particular annoyance (and apparently so do a lot of other people). Blogger themes are limited and while I can customize it I think a better solution is to move to another blogging platform.
← PreviousPage 2 of 2