Stable updates
The stable channel has been updated to 4.0.249.89 for Windows
The stable channel has been updated to 4.0.249.89 for Windows.
Stable Channel Update
The stable channel has been updated to 4.0.249.78 for Windows, and includes the following features and security fixes (since 3.0):
Google Chrome Stable channel (Windows) has been updated to version 3.0.195.38
Google Chrome's Stable channel has been updated to version 3.0.195.38. (The Stable channel is still Windows-only.)
This release fixes a couple of browser crashes:
- r31694 fixes a crash while typing in the omnibox (issue 20511).
- r32474 fixes a crash while playing mp4 videos with odd sizes, such as 1366x768 (issue 27675).
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.
Beta/Stable Channel Update
Both the beta and stable channel have been updated to 3.0.195.27 and contain the following fixes:
- Fixed an issue where menu items for certain Indian languages were not properly visible. (Issue: 18042)
- Add support to blacklist the faux www.paypal.com certificate. (Issue:24038)
Beta and Stable Channel Update
The beta and stable channels have been updated to 195.25. This release includes only a single change that adds an image link to the new tab page which directs new users to the themes gallery.
Anthony Laforge
Google Chrome Program Manager
Stable Channel Update
3.0.195.24 has been promoted to the stable channel. There are no additional fixes or changes in this release.
Security Fixes:
CVE-2009-0689 dtoa() error parsing long floating point numbers
The v8 engine uses a common dtoa() implementation to parse strings into floating point numbers. We have applied a patch to fix a recent bug in this component.
Stable Update: Security fixes
Google Chrome 2.0.172.43 has been released to the Stable channel to fix the security issues listed below.
CVE-2009-2935 Unauthorized memory read from Javascript
Stable, Beta update: Bug fixes
[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.
Stable, Beta update: Security fix
Google Chrome 2.0.172.33 has been released to the Stable and Beta channels. This release fixes a critical security issue and two other networking bugs.
CVE-2009-2121: Buffer overflow processing HTTP responses
Google Chrome is vulnerable to a buffer overflow in handling certain responses from HTTP servers. A specially crafted response from a server could crash the browser and possibly allow an attacker to run arbitrary code.
More info: http://code.google.com/p/
Severity: Critical. 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.
Stable update: 2 WebKit security fixes
Google Chrome's Stable channel has been updated to version 2.0.172.31 to fix two security issues in WebKit.
CVE-2009-1690 Memory corruption
A memory corruption issue exists in WebKit's handling of recursion in certain DOM event handlers. Visiting a maliciously crafted website may lead to a tab crash or arbitrary code execution in the Google Chrome sandbox. This update addresses the issue through improved memory management.
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.
Stable Update: Google Chrome 2.0.172.28
We're promoting 2.0.172 from Beta to the Stable channel today.
We've made a lot of changes to stuff you never see, such as a newer version of WebKit for rendering web pages, a new network stack, and improvements to speed up the V8 Javascript engine.
There are some new features like removing Most Visited sites from the New Tab page, form autofill, and full screen mode.
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.