Google has fixed more than 30 security vulnerabilities in its Chrome browser with a new version the company released on Friday. The company also paid out more than $14,000 in rewards to the various researchers who reported bugs that were fixed with Chrome 14.0.835.163.
The new version of Chrome includes fixes for 15 high-risk vulnerabilities, but none of the flaws in this release were rated critical by Google’s security team. The highest payout for one of the fixed bugs was a $2337 reward for Sergey Glazunov, who reported a bug that caused unintended access to V8 objects in Chrome. Many of the bugs fixed in this version of the browser were discovered by Google’s internal security team, which don’t qualify for the reward. However, the company still paid out $14,337 in bounties with this release.
Interestingly, Google also included a thank-you to a broad set of researchers–including some at Microsoft and Apple–for their work in helping to prevent certain flaws from ever making it into Chrome stable releases.
“In addition, we would like to thank ‘send.my.spam.to’, ‘Feiler89’, miaubiz, The Microsoft Java Team / Microsoft Vulnerability Research (MSVR), Chris Rohlf of Matasano, Chamal de Silva, Christian Holler, ‘simon.sarris’ and Alexey Proskuryakov of Apple for working with us in the development cycle and preventing bugs from ever reaching the stable channel. Various rewards were issued,” Google’s blog post said.
The full list of fixes in Chrome is:
-  High CVE-2011-2835: Race condition in the certificate cache. Credit to Ryan Sleevi of the Chromium development community.
-  Low CVE-2011-2836: Infobar the Windows Media Player plug-in to avoid click-free access to the system Flash. Credit to electronixtar.
- [Linux only]  Low CVE-2011-2837: Use PIC / pie compiler flags. Credit to wbrana.
-  Low CVE-2011-2838: Treat MIME type more authoritatively when loading plug-ins. Credit to Michal Zalewski of the Google Security Team.
-  High CVE-2011-2839: Crash in v8 script object wrappers. Credit to Kostya Serebryany of the Chromium development community.
-   Low CVE-2011-2840: Possible URL bar spoofs with unusual user interaction. Credit to kuzzcc.
- [$500]  High CVE-2011-2841: Garbage collection error in PDF. Credit to Mario Gomes.
- [Mac only]  Low CVE-2011-2842: Insecure lock file handling in the Mac installer. Credit to Aaron Sigel of vtty.com.
-  Medium CVE-2011-2843: Out-of-bounds read with media buffers. Credit to Kostya Serebryany of the Chromium development community.
-  Medium CVE-2011-2844: Out-of-bounds read with mp3 files. Credit to Mario Gomes.
- [$1000]  High CVE-2011-2846: Use-after-free in unload event handling. Credit to Arthur Gerkis.
- [$1000]  High CVE-2011-2847: Use-after-free in document loader. Credit to miaubiz.
- [$500]  Medium CVE-2011-2848: URL bar spoof with forward button. Credit to Jordi Chancel.
-  Low CVE-2011-2849: Browser NULL pointer crash with WebSockets. Credit to Arthur Gerkis.
- [$500]  Medium CVE-2011-3234: Out-of-bounds read in box handling. Credit to miaubiz.
-  Medium CVE-2011-2850: Out-of-bounds read with Khmer characters. Credit to miaubiz.
-  Medium CVE-2011-2851: Out-of-bounds read in video handling. Credit to Google Chrome Security Team (Inferno).
- [$500]  High CVE-2011-2852: Off-by-one in v8. Credit to Christian Holler.
-  High CVE-2011-2853: Use-after-free in plug-in handling. Credit to Google Chrome Security Team (SkyLined).
- [$1000]   High CVE-2011-2854: Use-after-free in ruby / table style handing. Credit to Sławomir Błażek, and independent later discoveries by miaubiz and Google Chrome Security Team (Inferno).
- [$1000]  High CVE-2011-2855: Stale node in stylesheet handling. Credit to Arthur Gerkis.
- [$2000]  High CVE-2011-2856: Cross-origin bypass in v8. Credit to Daniel Divricean.
- [$1000]  High CVE-2011-2857: Use-after-free in focus controller. Credit to miaubiz.
- [$1000]  High CVE-2011-2834: Double free in libxml XPath handling. Credit to Yang Dingning from NCNIPC, Graduate University of Chinese Academy of Sciences.
-  Medium CVE-2011-2859: Incorrect permissions assigned to non-gallery pages. Credit to Bernhard ‘Bruhns’ Brehm of Recurity Labs.
- [$1000]  High CVE-2011-2860: Use-after-free in table style handling. Credit to miaubiz.
-  Medium CVE-2011-2861: Bad string read in PDF. Credit to Aki Helin of OUSPG.
- [$2337]  High CVE-2011-2862: Unintended access to v8 built-in objects. Credit to Sergey Glazunov.
-  Medium CVE-2011-2864: Out-of-bounds read with Tibetan characters. Credit to Google Chrome Security Team (Inferno).
-  Medium CVE-2011-2858: Out-of-bounds read with triangle arrays. Credit to Google Chrome Security Team (Inferno).
-  Low CVE-2011-2874: Failure to pin a self-signed cert for a session. Credit to Nishant Yadant of VMware and Craig Chamberlain (@randomuserid).
- [$1000]  High CVE-2011-2852: Type confusion in v8 object sealing. Credit to Christian Holler.