Dinsdag is er weer een nieuwe stabiele versie van Googles webbrowser Chrome vrijgegeven. Van deze browser, die vooralsnog alleen voor Windows XP en Vista uitgebracht wordt, bestaan drie verschilende versies, te weten stable, bèta en developer preview, waardoor er voor ieder wat wils is. In deze release zijn twee ernstige beveiligingslekken gedicht, wordt er een nieuwere versie van Gears meegelevert en is het eenvoudiger om Google Chrome als standaard-browser in te stellen. De volledige release notes voor versie 1.0.154.64 zien er als volgt uit:
Stable Update: Security Fix
Google Chrome's Stable channel has been updated to version 1.0.154.64 to fix two security issues discovered by internal Google testing.
This release also containsSecurity Fixes
- A new notification at startup that makes it easier to set Google Chrome as the default browser. If you don't want Google Chrome to be the default browser, you can click 'Don't ask again'.
- A new version of Gears (0.5.16.0)
CVE-2009-1441: Input validation error in the browser process. A failure to properly validate input from a renderer (tab) process could allow an attacker to crash the browser and possibly run arbitrary code with the privileges of the logged on user. To exploit this vulnerability, an attacker would need to be able to run arbitrary code inside the renderer process.
More info: http://code.google.com/p/chromium/issues/detail?id=10869
Severity: Critical. An attacker might be able to run code with the privileges of the logged on user.
Mitigation: An attacker would need to be able to run arbitrary code in the renderer process.
CVE-2009-1442: Integer overflow in Skia 2D graphics. A failure to check the result of integer multiplication when computing image sizes could allow a specially-crafted image or canvas to cause a tab to crash and it might be possible for an attacker to execute arbitrary code inside the (sandboxed) renderer process.
More info: http://code.google.com/p/chromium/issues/detail?id=10736
Severity: High. An attacker might be able to run arbitrary code within the Google Chrome sandbox.
Mitigations:
- A victim would need to visit a page under an attacker's control.
- Any code that an attacker might be able to run inside the renderer process would be inside the sandbox. Click here for more details about sandboxing.