News for hackers. Stuff that matters.
Re:How Google set a trap for Pwn2Own exploit team by majmun on Saturday March 10, 2012 @09:13AM (#3687794)
Seems like a trap backfired -> https://www.google.com/support/forum/p/Chrome/thread?tid=687...

BTW I have to agree if vulnerable flash is included in default installation of chrome that is essentially the same thing as pwning chrome.

Re:How Google set a trap for Pwn2Own exploit team by justinschuh on Saturday March 10, 2012 @10:43AM (#3687934)
I wouldn't say it backfired, but after releasing we did discover that some Flash obfuscators used on games behave almost identically to a JIT spray attack. This is a shame because their obfuscation technique doesn't really add any value, but it does hurt performance, consume very large amounts of memory, and negatively impact stability. We've adjusted the detection to accommodate, and will make further adjustments as necessary.
Re:How Google set a trap for Pwn2Own exploit team by ootachi on Saturday March 10, 2012 @01:10PM (#3688280)
If causing crashes isn't backfiring, then I don't know what is.
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.
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.
Re:How Google set a trap for Pwn2Own exploit team by daeken on Saturday March 10, 2012 @08:27PM (#3689277)
I'm curious as to how you're doing JIT spray detection. Do you have any info on this?
Re:How Google set a trap for Pwn2Own exploit team by js2 on Saturday March 10, 2012 @11:19PM (#3689520)
See the links from http://news.ycombinator.com/item?id=3689491 - the bug in particular has some helpful commit comments, then read through http://src.chromium.org/viewvc/chrome/trunk/src/webkit/plugi...
Re:How Google set a trap for Pwn2Own exploit team by fruchtose on Saturday March 10, 2012 @02:16PM (#3688458)
To their credit, they pushed a fix the very next day. I would call that very minimal collateral damage. Google took responsibility in a timely manner for a non-critical bug.
Re:How Google set a trap for Pwn2Own exploit team by hammersend on Saturday March 10, 2012 @12:08PM (#3688121)
What would you suggest as an alternative? Not bundle flash? Then people will just download it anyway and many will end up with an old vulnerable version. At least with this the user can stay updated automatically with Chrome. The alternative is a net security net negative.
Re:How Google set a trap for Pwn2Own exploit team by majmun on Saturday March 10, 2012 @12:21PM (#3688155)
so i heard that java applets are similair vulnerability mess , so why not also bundle java with chrome? for net gain.
Re:How Google set a trap for Pwn2Own exploit team by mayanksinghal on Saturday March 10, 2012 @02:06PM (#3688438)
Because Java applets are not that popular anymore so there isn't much of a need. Javascript graphic apps are still slow, lack the smoothness and an experienced developer community that would build new games/apps or port old ones. As sad as it may be to accept it, flash is more popular and fully featured than most alernatives.

Who knows, Unity3D will substitute it for games, HTML5 Video /Sound for playing videos. While that happens, we will soon realize that Unity3D is another plugin-in-browser solution and might be (and I am just speculating here) vulnerable to issues similar to flash; while content providers will stop pushing video content because of lack of DRM like technology with HTML5 Videos. Please note that I am NOT supporting/rejecting any of the mentioned technologies; this is just a reply to a straw man argument.

Re:How Google set a trap for Pwn2Own exploit team by majmun on Saturday March 10, 2012 @02:58PM (#3688552)
I don't know about java being unpopular according to this site (first i could find in google) -> http://www.statowl.com/plugin_overview.php it has 75% of market share, second to flash with 95%. if you have some other numbers I would like to hear it.
Re:How Google set a trap for Pwn2Own exploit team by mayanksinghal on Saturday March 10, 2012 @03:39PM (#3688664)
Having the capability of loading applets is, I consider, not to be the same as popularity of applets. I am unable to produce any citation that talks about popularity of applets except this SO thread: http://stackoverflow.com/questions/51390/where-did-all-the-j...

But the lack of applets is pretty apparent to me. I come across Flash almost hourly while my last few encounters with Java Applets were academic demos 2 years back.