Re:How Google set a trap for Pwn2Own exploit team
by kevingadd on Saturday March 10, 2012 @02:18PM
(#3688465)
In the future you should consider not adding code like this to your browser, since it doesn't really add any value either.
[ Parent
| on HN ]
Re:How Google set a trap for Pwn2Own exploit team
by othermaciej on Saturday March 10, 2012 @03:16PM
(#3688604)
Based on what Justin said, it sounds like what they tried to add is a defense against JIT spray attacks, not just a detector, which, if effective, would actually be pretty valuable. JIT spray attacks are pretty dangerous, because they defeat many of the usual protections against exploiting buffer overflows for code execution (e.g. DEP and ASLR on Windows). So it certainly would be valuable to try to defend against these kind of attacks, if that is what the Chrome folks were doing.
Apparently it was not effective in the end, but we may never know, since VUPEN doesn't plan to disclose how they escaped the Chrome sandbox.
Re:How Google set a trap for Pwn2Own exploit team
by justinschuh on Saturday March 10, 2012 @08:25PM
(#3689274)
Yeah Maciej, that's the gist. The VUPEN guys told us it was effective at preventing the JIT spray, so they used an information leak to bypass ASLR/DEP.