I also love how much really good intelligent discussion happens here on things like PDFs that don't have a built-in commenting system.
So, thanks!
http://www.scienceblog.com/cms/computer-scientists-take-over...
It's not surprising that it's practical; it's basically just a souped up ret2libc attack.
Is that a fair statement?
deleteAllFiles user = if user == Root
then throwError "access denied"
else unsafeDeleteAllFiles
Even if memory access is safe, you can still type in the wrong algorithm.This attack is x86 machine-code-native, so Haskell in a VM is not vulnerable to the exact same problems, but to assume it's completely invulnerable is myopic.
This is completely false. Almost nobody in the software industry cares about safety. This can be proven trivially just by comparing how much more popular C and C++ are compared to memory-safe languages.
But for all practical purposes, you're right :)
2) hey, maybe we can get the music and film industry associations to mandate ECC as part of the license requirements for their next big DRM scheme
This paper is the moral equivalent of that post from yesterday about how you could derive all of ASCII from []()+! in Javascript. Here, the authors are trying to evade runtime defenses that prevent memory corruption exploits from uploading executable code in target processes. To control execution, they analyze target binaries and synthesize a turing complete runtime out of scraps of legitimate basic blocks.
From 34 instruction sequences, they essentially derive a VM with load/store/move, add/sub/neg/and/or/xor, conditional branches, and call (read the first couple pages and skip ahead to page 12 for the diagram of what "call" actually looks like when you scavenge it out of the bblocks of an unsuspecting program.
Obviously, once you have such a VM defined, you can compile arbitrary exploits to it. It's like having a scriptable debugger attached to the remote program.
You should read the paper because it's an excellent crash course in runtime exploit design and mitigation, and a good way to jog your x86 memory. But I should also note that I haven't done justice to the paper: it's thesis is that you can not only do all these things, but do them without the "ret" instruction, or any other non-innocuous sequence of instructions.