Chrome Releases: Stable, Beta update: Bug fixes

Chrome Releases

Release updates from the Chrome team

Stable, Beta update: Bug fixes

Thursday, July 16, 2009

[Update: Added CVE numbers for the security issues. --mal@chromium.org, 21 July 2009]Google Chrome 2.0.172.37 has been released to the Beta and Stable channels. This release fixes some minor bugs:

Fix: Solving captcha images broken at orkut.com. (Issue 15569)
Make forward/backward navigation work even when redirection is involved. (Issue 9663, issue 10531)
Fix: Daylight savings time not recognized for some CET locales. (Issue 12579)
Fix a browser crash on closing a URL request. (Issue 8942)
Update the V8 Javascript engine to version 1.1.10.14 to fix issues with regular expressions.
Update Gears to the latest release, 0.5.25.0.

In addition, this release fixes the following security issues:
CVE-2009-2555 Heap overflow with Javascript regular expressions
Evaluating a specially-crafted regular expression in Javascript on a web page can lead to memory corruption and possibly a heap overflow. Visiting a maliciously crafted website may lead to a renderer (tab) crash or arbitrary code execution in the Google Chrome sandbox.
More info: http://code.google.com/p/chromium/issues/detail?id=14719 (This issue will be made public once a majority of users are up to date with the fix.)

Severity: High. An attacker might be able to run arbitrary code within the Google Chrome sandbox.

Credit: This issue was found by the Google Chrome security team.

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.

CVE-2009-2556 Memory corruption in the browser process
A compromised renderer (tab) process could cause the browser process to allocate very large memory buffers. This error could cause the browser process (and all tabs) to crash or possibly allow arbitrary code execution 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.

Severity: Critical. In conjunction with a vulnerability allowing arbitrary code to run in the renderer, an attacker might be able to run code with the privileges of the logged on user.

Credit: This issue was found by the Google Chrome security team.

Mitigations:

A victim would need to visit a page under an attacker's control.
The attacker must exploit a second vulnerability to control the renderer process.

Labels: Beta updates , Stable updates

Labels

Admin Console 43
Android WebView 19
Beta 12
Beta updates 1122
chrome 1
Chrome Beta for Android 246
Chrome Dev for Android 4
Chrome for Android 141
Chrome for iOS 43
Chrome for Meetings 5
Chrome OS 936
Chrome OS Management 12
Chromecast Update 6
Desktop Update 398
dev update 108
Dev updates 1048
Flash Player update 5
Hangouts Meet hardware 5
Stable updates 677

Archive

2020
- Oct
- Sep
- Aug
- Jul
- Jun
- May
- Apr
- Mar
- Feb
- Jan

2019
- Dec
- Nov
- Oct
- Sep
- Aug
- Jul
- Jun
- May
- Apr
- Mar
- Feb
- Jan

2018
- Dec
- Nov
- Oct
- Sep
- Aug
- Jul
- Jun
- May
- Apr
- Mar
- Feb
- Jan

2017
- Dec
- Nov
- Oct
- Sep
- Aug
- Jul
- Jun
- May
- Apr
- Mar
- Feb
- Jan

2016
- Dec
- Nov
- Oct
- Sep
- Aug
- Jul
- Jun
- May
- Apr
- Mar
- Feb
- Jan

2015
- Dec
- Nov
- Oct
- Sep
- Aug
- Jul
- Jun
- May
- Apr
- Mar
- Feb
- Jan

2014
- Dec
- Nov
- Oct
- Sep
- Aug
- Jul
- Jun
- May
- Apr
- Mar
- Feb
- Jan

2013
- Dec
- Nov
- Oct
- Sep
- Aug
- Jul
- Jun
- May
- Apr
- Mar
- Feb
- Jan

2012
- Dec
- Nov
- Oct
- Sep
- Aug
- Jul
- Jun
- May
- Apr
- Mar
- Feb
- Jan

2011
- Dec
- Nov
- Oct
- Sep
- Aug
- Jul
- Jun
- May
- Apr
- Mar
- Feb
- Jan

2010
- Dec
- Nov
- Oct
- Sep
- Aug
- Jul
- Jun
- May
- Apr
- Mar
- Feb
- Jan

2009
- Dec
- Nov
- Oct
- Sep
- Aug
- Jul
- Jun
- May
- Apr
- Mar
- Feb
- Jan

2008
- Dec
- Nov
- Oct
- Sep

Give us feedback in our
Product Forums.

Google
Privacy
Terms