For several vulnerabilities

Jul 27, 2010 10:36 GMT  ·  By

The latest release of Google’s open source browser brings to the table patches for a few security vulnerabilities impacting previous releases. Users of Google Chrome are advised to upgrade as soon as possible to the latest iteration of the browser, namely Build 5.0.375.125, which is being served through the Stable channel. By updating, customers will ensure that they plug a few security holes, and that they will be safe against potential attacks. At this point in time, Google Chrome 5.0.375.125 is available for users running Linux, Mac, Windows.

Jason Kersey, from the Google Chrome team outlined no less than five vulnerabilities fixed with the advent of Chrome 5.0.375.125, three of which are considered to have a high security impact to users. The most severe vulnerabilities represent problems associated with large canvases, a memory corruption in rendering code, and another memory corruption in SVG handling.

However, it’s not just Chrome that’s getting security fixes. According to the Mountain View-based search giant, Build 5.0.375.125 of Chrome is also designed to implement a couple of workarounds for Critical vulnerabilities not in the browser itself, but in what Google called external components. Kersey revealed that one of the issues involved a Windows kernel bug, while the other a security problem resides in the GNU C library. Of course, users must understand that the measures taken by Google are mere workarounds, and not actual patches.

Users should get used to seeing more and more Stable releases of Google Chrome in the next few months and moving onward. Google currently plans to release a new Chrome Stable release once every six weeks, twice as often as it does today. The Mountain View company confirmed that it is accelerating the release process for Chrome the past week, when it emphasized the need to get new features to end users as soon as possible.

Google Chrome 5.0.375.125 Stable for Windows is available for download here.

Follow me on Twitter @MariusOiaga.