Google Fixes 51 Bugs in Chrome 41

Google released the latest build of its browser Tuesday, Chrome 41.0.2272.76, patching 51 different bugs and paying out over $50,000 in bounties.

Google released the latest build of its browser Tuesday, Chrome 41.0.2272.76, patching 51 different bugs and paying out over $50,000 in bounties.

Google paid bounties for 18 bugs ranging from medium to high severity. The bounties for all of the vulnerabilities totaled $52,000.

13 of those bugs came marked with a severity rating of high and largely stem from either an out-of-bounds, use-after-free or integer overflow vulnerability.

According to a blog posted by Google’s Penny MacNeil yesterday, Chrome’s team also implemented a handful of fixes from internal audits and fuzzing. Additionally, Chrome developers also made updates to the company’s open source JavaScript engine, V8.

Here’s the full rundown of bugs contributed by external researchers fixed in this edition of Chrome:

[$7500][456516] High CVE-2015-1212: Out-of-bounds write in media. Credit to anonymous.
[$5000][448423] High CVE-2015-1213: Out-of-bounds write in skia filters. Credit to cloudfuzzer.
[$5000][445810] High CVE-2015-1214: Out-of-bounds write in skia filters. Credit to cloudfuzzer.
[$5000][445809] High CVE-2015-1215: Out-of-bounds write in skia filters. Credit to cloudfuzzer.
[$4000][454954] High CVE-2015-1216: Use-after-free in v8 bindings. Credit to anonymous.
[$3000][456192] High CVE-2015-1217: Type confusion in v8 bindings. Credit to anonymous.
[$3000][456059] High CVE-2015-1218: Use-after-free in dom. Credit to cloudfuzzer.
[$3000][446164] High CVE-2015-1219: Integer overflow in webgl. Credit to Chen Zhang (demi6od) of NSFOCUS Security Team.
[$3000][437651] High CVE-2015-1220: Use-after-free in gif decoder. Credit to Aki Helin of OUSPG.
[$2500][455368] High CVE-2015-1221: Use-after-free in web databases. Credit to Collin Payne.
[$2500][448082] High CVE-2015-1222: Use-after-free in service workers. Credit to Collin Payne.
[$2000][454231] High CVE-2015-1223: Use-after-free in dom. Credit to Maksymillian Motyl.
[449610] High CVE-2015-1230: Type confusion in v8. Credit to Skylined working with HP’s Zero Day Initiative.
[$2000][449958] Medium CVE-2015-1224: Out-of-bounds read in vpxdecoder. Credit to Aki Helin of OUSPG.
[$1000][446033] Medium CVE-2015-1225: Out-of-bounds read in pdfium. Credit to cloudfuzzer.
[$1000][456841] Medium CVE-2015-1226: Validation issue in debugger. Credit to Rob Wu.
[$1000][450389] Medium CVE-2015-1227: Uninitialized value in blink. Credit to Christoph Diehl.
[$1000][444707] Medium CVE-2015-1228: Uninitialized value in rendering. Credit to miaubiz.
[$500][431504] Medium CVE-2015-1229: Cookie injection via proxies. Credit to iliwoy.

Those looking for a full list of changes can find them in the Chromium changelog.

A Google spokesperson on Wednesday claimed that the way Android connects to most websites, including Google sites and others without export certificates are not subject to the FREAK flaw that’s dominated headlines this week. The flaw enables attackers to downgrade their victims’ SSL clients RSA key and compromise their connections with a man-in-the-middle attack.

“We encourage all websites to disable support for export certificates, Google said before adding that its “developed a patch to protect Android’s connection to sites that do expose export certs and that patch has been provided to partners.”

Suggested articles

Discussion

  • Anonymous on

    What's an export certificate? Do you mean ciphersuite?

Subscribe to our newsletter, Threatpost Today!

Get the latest breaking news delivered daily to your inbox.