The Chrome team is delighted to announce the promotion of Chrome 37 to the stable channel for Windows, Mac and Linux. Chrome 37.0.2062.94 contains a number of fixes and improvements, including:
- DirectWrite support on Windows for improved font rendering
- A number of new apps/extension APIs
- Lots of under the hood changes for stability and performance
A full list of changes is available in the log.
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 50 security fixes. Below, we highlight fixes that were either contributed by external researchers or particularly interesting. Please see the Chromium security page for more information.
[$30000] Critical CVE-2014-3176, CVE-2014-3177: A special reward to lokihardt@asrt for a combination of bugs in V8, IPC, sync, and extensions that can lead to remote code execution outside of the sandbox.
[$2000] High CVE-2014-3168: Use-after-free in SVG. Credit to cloudfuzzer.
[$2000] High CVE-2014-3169: Use-after-free in DOM. Credit to Andrzej Dyjak.
[$1000] High CVE-2014-3170: Extension permission dialog spoofing. Credit to Rob Wu.
[$4000] High CVE-2014-3171: Use-after-free in bindings. Credit to cloudfuzzer.
[$1500] Medium CVE-2014-3172: Issue related to extension debugging. Credit to Eli Grey.
[$2000] Medium CVE-2014-3173: Uninitialized memory read in WebGL. Credit to jmuizelaar.
[$500] Medium CVE-2014-3174: Uninitialized memory read in Web Audio. Credit to Atte Kettunen from OUSPG.
We would also like to thank Collin Payne, Christoph Diehl, Sebastian Mauer, Atte Kettunen, and cloudfuzzer for working with us during the development cycle to prevent security bugs from ever reaching the stable channel. $8000 in additional rewards were issued.
As usual, our ongoing internal security work responsible for a wide range of fixes:
 CVE-2014-3175: Various fixes from internal audits, fuzzing and other initiatives (Chrome 37).
Many of the above bugs were detected using AddressSanitizer and MemorySanitizer.
Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug.