Google heeft de stable-versie van versie 49 van zijn webbrowser Chrome uitgebracht. Google Chrome is beschikbaar voor Windows, Linux en OS X. Er zijn ook versies voor Android en iOS, maar die volgen een iets ander releaseschema. Bij het brengen van versie 49 naar het stable-kanaal zijn er 26 beveiligingsproblemen verholpen, waarvoor Google sommige ontdekkers beloond heeft.
Security Fixes and RewardsNote: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed.
This update includes 26 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chromium security page for more information.
- [$8000][560011] High CVE-2016-1630: Same-origin bypass in Blink. Credit to Mariusz Mlynski.
- [$7500][569496] High CVE-2016-1631: Same-origin bypass in Pepper Plugin. Credit to Mariusz Mlynski.
- [$5000][549986] High CVE-2016-1632: Bad cast in Extensions. Credit to anonymous.
- [$3000][572537] High CVE-2016-1633: Use-after-free in Blink. Credit to cloudfuzzer.
- [$3000][559292] High CVE-2016-1634: Use-after-free in Blink. Credit to cloudfuzzer.
- [$2000][585268] High CVE-2016-1635: Use-after-free in Blink. Credit to Rob Wu.
- [$2000][584155] High CVE-2016-1636: SRI Validation Bypass. Credit to Ryan Lester and Bryant Zadegan.
- [$500][560291] High CVE-2015-8126: Out-of-bounds access in libpng. Credit to joerg.bornemann.
- [$2000][555544] Medium CVE-2016-1637: Information Leak in Skia. Credit to Keve Nagy.
- [$1000][585282] Medium CVE-2016-1638: WebAPI Bypass. Credit to Rob Wu.
- [$1000][572224] Medium CVE-2016-1639: Use-after-free in WebRTC. Credit to Khalil Zhani.
- [$1000][550047] Medium CVE-2016-1640: Origin confusion in Extensions UI. Credit to Luan Herrera.
- [$500][583718] Medium CVE-2016-1641: Use-after-free in Favicon. Credit to Atte Kettunen of OUSPG.
We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel. An additional $14,500 in rewards were issued for security bugs present on non-stable channels.
As usual, our ongoing internal security work was responsible for a wide range of fixes:
- [591402] CVE-2016-1642: Various fixes from internal audits, fuzzing and other initiatives.
- Multiple vulnerabilities in V8 fixed at the tip of the 4.9 branch (currently 4.9.385.26).
Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, Control Flow Integrity or LibFuzzer.