Security Fixes and Rewards
Note: 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 15 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chromium security page for more information.
[$7500] High CVE-2016-1696: Cross-origin bypass in Extension bindings. Credit to anonymous.
[$7500] High CVE-2016-1697: Cross-origin bypass in Blink. Credit to Mariusz Mlynski.
[$4000] Medium CVE-2016-1698: Information leak in Extension bindings. Credit to Rob Wu.
[$3500] Medium CVE-2016-1699: Parameter sanitization failure in DevTools. Credit to Gregory Panakkal.
[$1500] Medium CVE-2016-1700: Use-after-free in Extensions. Credit to Rob Wu.
[$1000] Medium CVE-2016-1701: Use-after-free in Autofill. Credit to Rob Wu.
[$1000] Medium CVE-2016-1702: Out-of-bounds read in Skia. Credit to cloudfuzzer.
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.
As usual, our ongoing internal security work was responsible for a wide range of fixes:
-  CVE-2016-1703: Various fixes from internal audits, fuzzing and other initiatives.
Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, Control Flow Integrity or LibFuzzer.
A list of changes is available in the log. Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.
Krishna GovindGoogle Chrome