So as most of you probably know the big buzz on the Internet last week was that Google (after supporting Firefox for so long) have actually launched their own browser.
It’s cooled Google Chrome. Now of course in typical Google fashion they call it BETA software, and a number of flaws have popped up during the first couple of days of release.
One cool thing though is that each tab runs it’s own threaded process, so if one tab bombs out it won’t take down your whole browser.
The browser is a move for Google into the online/offline integration they started with Google Desktop, there are more and more online apps (Google Office) that people still want to use offline with a Google made browser this will be possible.
You also have to consider the privacy implications though, if you are also using Gmail…Google will basically know everything you do, even worse if you also use Google Desktop they will know what you have on your computer, what e-mail you send and receive and what you surf on the web.
There have been a few flaws released since Chrome came out such as a carpet bombing flaw:
Google’s shiny new Web browser is vulnerable to a carpet-bombing vulnerability that could expose Windows users to malicious hacker attacks.
Just hours after the release of Google Chrome, researcher Aviv Raff discovered that he could combine two vulnerabilities — a flaw in Apple Safari (WebKit) and a Java bug discussed at this year’s Black Hat conference — to trick users into launching executables direct from the new browser.
The PoC is here: http://raffon.net/research/google/chrome/carpet.html
Another is a crash in chrome.dlll.
An issue exists in how chrome behaves with undefined-handlers in chrome.dll version 0.2.149.27. A crash can result without user interaction. When a user is made to visit a malicious link, which has an undefined handler followed by a ‘special’ character, the chrome crashes with a Google Chrome message window “Whoa! Google Chrome has crashed. Restart now?”. It fails in dealing with the POP EBP instruction when pointed out by the EIP register at 0x01002FF4.
The PoC is here: http://evilfingers.com/advisory/google_chrome_poc.php
And a few people have also been complaining that it allows auto-download of executable without a user prompt.
We will be keeping an eye on Google Chrome.
Recent in Exploits/Vulnerabilities:
- Cupid Media Hack Exposes 42 Million Passwords In Plain Text
- Linux Backdoor Fokirtor Injects Traffic Into SSH Protocol
- Another IE 0-Day Hole Found & Used By In-Memory Drive By Attacks
- Google Patches 32 Chrome Browser Bugs & Releases Version 14
- Google Willing To Pay Bounty For Chrome Browser Bugs
- Google Chrome Set To Follow Firefox In Blocking Out-of-date Plug-ins
Most Read in Exploits/Vulnerabilities:
- Learn to use Metasploit – Tutorials, Docs & Videos - 222,890 views
- AJAX: Is your application secure enough? - 118,523 views
- eEye Launches 0-Day Exploit Tracker - 84,955 views