The latest update introduced to the Stable version of the Google browser is designed to resolve an issue in which Chrome does not start. On November 12, 2009, the Mountain View-based search giant started pushing Google Chrome 3.0.195.33 through the Stable channel. In addition to the startup problem, the latest update to Chrome is also set up to patch a vulnerability affecting the previous Stable release of the open source browser.
“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,”
revealed Mark Larson, Google Chrome Team. “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.”
The 3.0.195.33 version comes at just a week since the previous update to the Chrome Stable channel. In the first week of November, Google released a security and stability refresh for the browser, taking Chrome to 3.0.195.32 at the time. Following that release, the Chrome Dev channel was also updated, with
v4.0.237.0, a Build focused on stability improvements, extensibility enhancements, and softening the rough corners of the browser. At the start of this month, Google Chrome version 4.0 evolved into
Beta stage, with version 4.0.223.16 now being offered to all participants in the Beta testing program.
The security vulnerability dealt with in Google Chrome 3.0.195.33 involves “CVE-2009-2816 Custom headers incorrectly sent for CORS OPTIONS request,” according to Larson. “A malicious web site operator could set custom HTTP headers on cross-origin OPTIONS requests. A victim would need to visit a page under an attacker's control. The OPTIONS attribute is not widely supported by servers.”
The latest releases of Google Chrome are available for download
here.
Find us on Google+
No user comments yet.
Be the first to express your opinion!
