Finally I can talk about what I’ve been doing since I left Microsoft: I’ve been working on security for Google Chrome; trying to find as many vulnerabilities before we shipped the beta. In the process I’ve found plenty of bugs in other browsers as well 
. I’m looking forward to the first real externally found security vulnerability; there have been some reports about crashes but nothing that allows an attacker to completely compromise the machine… we’ll see what happens!
Quick links
-
Categories
- Art (3)
- ASCII Art (2)
- Browsers (40)
- Chrome (11)
- Extensions (1)
- Firefox (14)
- Plugins (5)
- Internet Explorer (16)
- Opera (8)
- Safari (10)
- Chrome (11)
- Debugging (2)
- Email (1)
- Funny (6)
- Popups (3)
- Google (11)
- HTTP servers (1)
- Imagine Cup (7)
- Instant Messaging (1)
- Live Messenger (1)
- MediaWiki (2)
- notepad++ (1)
- Programming Languages (52)
- Registry (4)
- Security (38)
- Uncategorized (9)
- Video (2)
- YouTube (1)
- Art (3)
-
Archives
- November 2011
- May 2011
- January 2011
- December 2010
- November 2010
- October 2010
- September 2010
- August 2010
- July 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- October 2009
- September 2009
- August 2009
- July 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- October 2008
- September 2008
- August 2008
- July 2008
- May 2008
- April 2008
4 Comments to “Google Chrome released”
2008/09/05
Have you looked into the SaveAs BoF PoC on Milworm?
http://www.milw0rm.com/exploits/6367
2008/09/06
Well, as of Sept. 6th, There are a few interesting exploits available already, including 4 DoS exploits, 2 Arbitrary File Downloads, and a Buffer Overflow. Of the Downloaders one uses JavaScript’s window.setTimeout and the other uses a Meta tag. It also stores saved Passwords in Plain Text. All are available @ PacketStorm of course.
All in all, you might want to make some improvements in it’s security before actually pushing for any release to the unwashed masses
2008/09/11
Nice Work!
2008/09/16
Because I work in Google Chrome’s security, I do get to see all the “exploits”. However, I have yet to see a working exploit that actually compromises an up-to-date OS. So far I’ve seen “exploits” that require a victim to do all kinds of random things and can only compromise older versions of Windows without hardware DEP.
Furthermore, this is a beta release (http://en.wikipedia.org/wiki/Software_release_life_cycle#Beta). Quoting wikipedia: “Beta testing allows the software to undergo usability testing with users who provide feedback, so that any malfunctions these users find in the software can be reported to the developers and fixed. Beta software can be unstable and could cause crashes or data loss.”
That said, this does not mean I’m happy for Google Chrome to have security vulnerabilities. It’s my job to find this bugs before anybody else does, so in a way, I have failed. When we find out about a vulnerability, either internally or through an external report, we try to analyze the issue and fix it as soon as possible. I think you’ll find that most of the bugs you mentioned are already fixed in the latest release or will be fixed in the next.
Leave a Comment