Stable Channel Update for Chrome OS

The Stable channel has been updated to 50.0.2661.103, 50.0.2661.104 (Platform version: 7879.74.0, 7978.76.0) for all Chrome OS devices except Pinky 11.6" Chromebooks and Asus Chromebit. This build contains a number of bug fixes, security updates, and feature enhancements. Systems will be receiving updates over the next several days.

Some highlights of these changes are:

• Bluetooth names clearer and consistent
• Chrome browser updated to use material design

If you find new issues, please let us know by visiting our forum or filing a bug. Interested in switching channels? Find out how. You can submit feedback using ‘Report an issue...’ in the Chrome menu (3 vertical dots in the upper right corner of the browser) or by pressing Alt+Shift+I.

Ketaki Deshpande

Google Chrome

Stable Channel Update

The stable channel has been updated to 50.0.2661.102 for Windows, Mac, and Linux.

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 5 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chromium security page for more information.

[$8000][605766] High CVE-2016-1667: Same origin bypass in DOM. Credit to Mariusz Mlynski.

[$7500][605910] High CVE-2016-1668: Same origin bypass in Blink V8 bindings. Credit to Mariusz Mlynski.

[$3000][606115] High CVE-2016-1669: Buffer overflow in V8. Credit to Choongwoo Han.

[$1337][578882] Medium CVE-2016-1670: Race condition in loader. Credit to anonymous.

[$500][586657] Medium CVE-2016-1671: Directory traversal using the file scheme on Android. Credit to Jann Horn.

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.

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 Govind

Google Chrome