3 ms·
So it's just an "if we would have a hole, we could use it." They used the "recently patched" hole (that is, the unpatched system) for their submission to Micros
by acqq 12y ago
So it's just an "if we would have a hole, we could use it." They used the "recently patched" hole (that is, the unpatched system) for their submission to Microsoft, and the custom kernel driver they crafted for this article. Unsurprisingly, Microsoft's response was "yes, we know, no, you don't qualify."
- Someone1234 12y agoIt is an impressive piece of research that bypasses several key pieces of kernel protection. It could definitely be utilised by a kernel mode exploit in the future to expand limited access into a full blown piece of running kernel code. I don't really have an opinion on Microsoft's response one way or the other. They get to set the rules on their own bug bounty and that is that. Also to fix this would almost certainly require a large scale kernel re-write (as the article itself alludes to).
- acqq 12y agoAs far as I understand, their demo is dependent on their kernel mode driver through which a user mode application can write to any memory address with the "root" privileges. So it demonstrates that if you already have the "root" "write" privileges, you can bypass the protections provided by the kernel. I fail to see what exactly is impressive then. Raymond Chen would probably cite the following segment from "The Hitchhiker's Guide to the Galaxy" ""We're trapped now aren't we?" "Yes," said Ford, "we're trapped." "Well didn't you think of anything? I thought you said you were going to think of something. Perhaps you thought of something and didn't notice." "Oh yes, I thought of something," panted Ford. Arthur looked up expectantly. "But unfortunately," continued Ford, "it rather involved being on the other side of this airtight hatchway." He kicked the hatch they'd just been through."
- makomk 12y agoThe mitigations they're talking about bypassing are, like all mitigation techniques, intended to ensure that if someone has a security hole they cannot make use of it. That's their entire point; if there were no security holes, there'd be no need for stuff like DEP, SMEP, and ASLR in the first place. In practice that's not a realistic assumption, which is why companies like Intel have gone to the trouble of adding hardware features that have zero benefit unless there's a security hole in the operating system.
- acqq 12y agoDEP, SMEP, ASLR are there to make the user-mode exploits harder. But if that bypass depends on having the "root" "write anywhere" hole, well, it uses the quite a big hole, and they just demonstrate that it is actually a big one. As far as I undestand, DEP and SMEP simply use the VM page flags controlled by the "root." The article authors depend on having the "root" write access to the given flags, and then they claim that they "bypass" DEP and SMEP, whereas they actually change the mentioned flags. They also explain that as soon as they have that, they simply aren't constrained by the ASLR at all.