Software Update: Google Chrome 27.0.1453.110

Google has released an update to version 27 of its Chrome web browser. Google Chrome is available in three different versions: stable, beta and dev, and this time the stable version has been updated. New in version 27 is the chrome.syncFileSystem API, which gives apps the ability to store specific data on Google Drive for availability on different clients and platforms. In addition, pages load on average five percent faster and improvements have been made to the spell checker and Omnibox. In addition, there are of course the necessary security updates and bug fixes. The changelog for this update only shows security updates.

Security fixes and rewards:

please see the Chromium security page for more information. (Note that the referenced bugs may be kept private until a majority of our users are up to date with the fix.)

This automatic update includes security fixes. We’d like to highlight the following fixes for various reasons (crediting external researchers, issuing rewards, or highlighting particularly interesting issues):

• [Windows only] [243339] High CVE-2013-2854: Bad handle passed to renderer.
• [242322] Medium CVE-2013-2855: Memory corruption in dev tools API.
• [242224] High CVE-2013-2856: Use after free in input handling.
• [240124] High CVE-2013-2857: Use after free in image handling.
• [239897] High CVE-2013-2858: Use after free in HTML5 Audio.
• [237022] High CVE-2013-2859: Cross-origin namespace pollution.
• [225546] High CVE-2013-2860: Use-after-free with workers accessing database APIs.
• [209604] High CVE-2013-2861: Use after free with SVG.
• [161077] High CVE-2013-2862: Memory corruption in Skia GPU handling.
• [232633] Critical CVE-2013-2863: Memory corruption in SSL socket handling.
• [239134] High CVE-2013-2864: Bad free in PDF viewer.

In addition, our ongoing internal security work was as usual responsible for a wide range of fixes:

• [246389] High CVE-2013-2865: Various fixes from internal audits, fuzzing and other initiatives.

Full details about what changes are in this build are available in the SVN revision log. Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug.