4 ms·
The Chrome sandbox protects pretty well against that kind of exploit. I bet $20K [1] that won't own Chrome. Also, I think Android 2.3.3 patches the webkit bug -
by nl 16y ago
The Chrome sandbox protects pretty well against that kind of exploit. I bet $20K [1] that won't own Chrome. Also, I think Android 2.3.3 patches the webkit bug - there was a similar problem that held up the release somewhat.
(Obviously that shouldn't understate the danger of that exploit against Safari or the Android browser)
[1] of Google's money: http://dvlabs.tippingpoint.com/blog/2011/02/02/pwn2own-2011 http://dvlabs.tippingpoint.com/blog/2011/02/02/pwn2own-2011
- iuguy 16y agoThe Sandbox makes things harder, but it's not infallible and has been bypassed before. For a pretty good walkthrough of the source (with links to even better more in-depth walkthroughs) have a look here: http://www.breakingpointsystems.com/community/blog/chrome-sandbox/ http://www.breakingpointsystems.com/community/blog/chrome-sa...
- nl 16y agoOf course the sandbox isn't failsafe, but it's pretty decent. I don't think there have been any remotely exploitable holes found in it yet, have they? (Thats a good link, and links to some security bugs found in the sandbox. But I don't think any of those have ever had a live remote exploit)