Reporter Chris Brook
Google has fixed 30 bugs in version 13.0.782.107, the latest build of its Chrome browser, pushed to the stable channel for Windows, Mac and Linux today.
14 of the bugs are deemed high-risk, including cross-origin script injection, HTML range handling and URI handling issues. Nine of the bugs are rated medium priority while just seven are rated low.
September 1, 2016 , 11:52 am
August 17, 2016 , 12:54 pm
August 15, 2016 , 5:10 pm
Through the company’s bug bounty program this round of patches paid $17,000 to researchers, one of the largest pay-outs yet. Much like June’s update, a researcher named Miaubiz found the most flaws in Chrome this time through, reporting eight of them to Google for a total of $7,500.
$3000 was awarded to Sergey Glazunov for cross-origin script injection bug and the cross-origin violation in base URI handling bug, among others. The Russian researcher was the first to receive Google’s “elite” $3,133.7 bounty after reporting a critical “stale pointer” flaw in January.
The list of security bugs fixed in Chrome 13.0.782.107 is as follows:
-  Medium CVE-2011-2358: Always confirm an extension install via a browser dialog. Credit to Sergey Glazunov.
- [$1000 each]  High CVE-2011-2359: Stale pointer due to bad line box tracking in rendering. Credit to miaubiz and Martin Barbella. Low CVE-2011-2360: Potential bypass of dangerous file prompt. Credit to kuzzcc.
-  Low CVE-2011-2361: Improve designation of strings in the basic auth dialog. Credit to kuzzcc.
- [Linux only]  Medium CVE-2011-2782: File permissions error with drag and drop. Credit to Evan Martin of the Chromium development community.
-  Medium CVE-2011-2783: Always confirm a developer mode NPAPI extension install via a browser dialog. Credit to Sergey Glazunov.
-  Low CVE-2011-2784: Local file path disclosure via GL program log. Credit to kuzzcc.
-  Low CVE-2011-2785: Sanitize the homepage URL in extensions. Credit to kuzzcc.
-  Low CVE-2011-2786: Make sure the speech input bubble is always on-screen. Credit to Olli Pettay of Mozilla.
-  Medium CVE-2011-2787: Browser crash due to GPU lock re-entrancy issue. Credit to kuzzcc.
-  Low CVE-2011-2788: Buffer overflow in inspector serialization. Credit to Mikołaj Małecki.
- [$500 each]  Medium CVE-2011-2789: Use after free in Pepper plug-in instantiation. Credit to Mario Gomes and kuzzcc.
- [$1000]  High CVE-2011-2790: Use-after-free with floating styles. Credit to miaubiz.
- [$1000]  High CVE-2011-2791: Out-of-bounds write in ICU. Credit to Yang Dingning from NCNIPC, Graduate University of Chinese Academy of Sciences.
- [$1000]  High CVE-2011-2792: Use-after-free with float removal. Credit to miaubiz.
- [$1000]  High CVE-2011-2793: Use-after-free in media selectors. Credit to miaubiz.
- [$500]  Medium CVE-2011-2794: Out-of-bounds read in text iteration. Credit to miaubiz.
- [$500]  Medium CVE-2011-2795: Cross-frame function leak. Credit to Shih Wei-Long.
-  High CVE-2011-2796: Use-after-free in Skia. Credit to Google Chrome Security Team (Inferno) and Kostya Serebryany of the Chromium development community.
- [$1000]  High CVE-2011-2797: Use-after-free in resource caching. Credit to miaubiz.
-  Low CVE-2011-2798: Prevent a couple of internal schemes from being web accessible. Credit to sirdarckcat of the Google Security Team.
- [$1000]  High CVE-2011-2799: Use-after-free in HTML range handling. Credit to miaubiz.
- [$500]  Medium CVE-2011-2800: Leak of client-side redirect target. Credit to Juho Nurminen.
- [$1000]  High CVE-2011-2802: v8 crash with const lookups. Credit to Christian Holler.
-  Medium CVE-2011-2803: Out-of-bounds read in Skia paths. Credit to Google Chrome Security Team (Inferno).
- [$1000]  High CVE-2011-2801: Use-after-free in frame loader. Credit to miaubiz.
- [$1000]  High CVE-2011-2818: Use-after-free in display box rendering. Credit to Martin Barbella.
- [$500]  High CVE-2011-2804: PDF crash with nested functions. Credit to Aki Helin of OUSPG.
- [$1500]  High CVE-2011-2805: Cross-origin script injection. Credit to Sergey Glazunov.
- [$1500]  High CVE-2011-2819: Cross-origin violation in base URI handling. Credit to Sergey Glazunov.