Web browsers are serious risk surfaces, so there's always room for a better one - but so far, most new browsers are a lot dumber than the incumbents.
So it was with Apple's Safari, when that was ported to Windows as a beta -it was found to be exploitable within two hours of release. So it is with Google's Chrome, which should be no surprise as it uses the pre-fixed exploited code from Safari!
Google talk a good talk, with these security features widely quoted:
- Privacy mode for trackless browsing
- Each tab runs in its own context, can't crash other tabs
- Tabs run in a "sandbox", can't attack the rest of the system
- Updates list of bad sites from Google's servers, to spot phishing scams
- Web pages can open without browser UI elements (uhh... why is this "secure"?)
My first reaction when I read this was, "wow, Google scooped IE8's feature set", given that IE8 builds IE7's to phishing filter into a more comprehensive updated system, runs tabs in separate processes so they don't crash the whole browser, and Vista runs IE7 and thus IE8 in a safer "protected mode" for well over a year now. I don't know whether Google's "sandbox" is stronger and safer than IE7-on-Vista's "protected mode", or whether either of these constitute an effective "sandbox".
Then I thought: Hang on, this is a newly-released beta, whereas IE8 has been in beta for a while now and has already been more widely released as beta 2... so who's first to offer these features?
I have to wonder why Google thinks it's a good idea to spawn web content (basically, stuff foisted from the web) as generic stand-alone windows, when we already have so many problems with pop-ups forging system dialog boxes to push fake scanners etc. Why is it considered a good idea to let sites hide the address bar, when phishing attacks so often use misleading URLs that HTML allows to be covered with arbitrary text, including completely different fake URLs?
So it doesn't bode well, that the public beta they release is based on a known-exploitable code base, which is already being attacked, at a time when patched versions of this code are already being retro-fitted to existing Safari installations.
Why would Google not build their beta on the fixed code base? It's Open Source, and already available, why not use it? Would it have killed them to delay the hitherto-secret web browser beta until they'd adopted the fixed code? Or is the need to leverage pre-arranged hype etc. more important than shipping known-exploited code to users? And why does the fixed release still report the exploitable code base version?
Trust me, I'm a software vendor
"Users do not get a notification when they are updated. When there are security fixes, it's crucial that we update our users as quickly as possible in order to keep them safe. Thus, it's important for us to not require user intervention. There are some security fixes that we'll keep quiet because we don't want to disclose security vulnerabilities to attackers"
To me, that reads like a dangerous combination of Mickey-Mouse attempts at security via obscurity, plus supreme vendor arrogance.
But wait, there's more...
Further things have come to light when searching for links for this post, such as installing in a "data" location (thus side-stepping Vista's protection for "Program Files") and a rather too-effective search that finds supposedly private things.
"Well, it's a beta", I can hear you say. That's why it's safely tucked away deeply within Google's developer site, so that only the adventurous and knowledgeable will find it, right? I mean, it's not as if it's being shoved at everyone via popular or vendor-set web pages so that it's gaining significant market share, is it?