Software Update: Google Chrome 3.0.195.33

Google has released another release of its Chrome browser, this time with 3.0.195.33 as the version number. In version 3.0.x, the speed of the program has been worked on, among other things. Other notable improvements are the new tab page and the extension of the HTML5 capabilities, for example the

Stable Update: Fix Google Chrome not Starting

Google Chrome’s Stable channel has been updated to 3.0.195.33 to fix a potential issue that could cause Google Chrome to stop working and a security issue.

This release removes a dependency on a Windows library (t2embed.dll) that is not required by Google Chrome. If that library is missing or the user does not have permission to read it, earlier versions of Google Chrome would fail silently.

Security Fix:
CVE-2009-2816 Custom headers incorrectly sent for CORS OPTIONS request
A malicious web site operator could set custom HTTP headers on cross-origin OPTIONS requests.
More info: https://bugs.webkit.org/show_bug.cgi?id=28446.

Stable Channel Update

The stable channel has been updated to 3.0.195.32, and includes the following security and stability fixes:

• Resolved a history issue that affected going back from queries in Google Maps. (Issue: 21353)
• Fixed issue with Adobe Acrobat Reader 9.2, where no content would be displayed. (Issue: 24883)
• Fixed an infinite loop in AAC decoding. (Web Kit Issue: 27239)
• Fixed a top crasher. (Issue: 22205)
• Fix issues where setInterval sometimes eats 100% CPU. (Issue: 25892)

Security Fixes:

CVE-2009-XXXX User not warned for some file types that can execute JavaScript
The user was not warned about certain possibly dangerous file types such as SVG, MHT and XML files. In some browsers, JavaScript can execute within these types of files. Because the JavaScript runs in the local context, it may be able to access local resources.
More info: http://code.google.com/p/chromium/issues/detail?id=23979
(This issue will be made public once a majority of users are up to date with the fix.)

CVE-2009-XXXX Possible memory corruption in the Gears plugin
A malicious site could use the Gears SQL API to put SQL metadata into a bad state, which could cause a subsequent memory corruption. This may lead to a Gears plugin crash or possibly arbitrary code execution.
More info: http://code.google.com/p/chromium/issues/detail?id=26179
(This issue will be made public once a majority of users are up to date with the fix.)