Google Chrome 11.0.696.57

Google heeft versie 11 zijn webbrowser Chrome stabiel verklaard. Google Chrome is beschikbaar in drie verschillende uitvoeringen, te weten stable, bèta en dev. Developmentversies zitten in een vroeg stadium van ontwikkeling en zijn dus het minst stabiel. In versie 11 treffen we onder andere de mogelijkheid aan om tekst via spraak in te voeren. Daarnaast zijn er natuurlijk weer de nodige bugfixes doorgevoerd en beveiligingsproblemen verholpen.

Chrome Stable Update

The Google Chrome team is happy to announce the arrival of Chrome 11.0.696.57 to the Stable Channel for Windows, Mac, Linux, and Chrome Frame. Chrome 11 contains some really great improvements including speech input through HTML.

Security fixes and rewards:

Please see the Chromium security page for more detail. Note that the referenced bugs may be kept private until a majority of our users are up to date with the fix.

We’re pleased to associate a record $16,500 of rewards with this patch.

• [61502] High CVE-2011-1303: Stale pointer in floating object handling. >Credit to Scott Hess of the Chromium development community and Martin Barbella.
• [70538] Low CVE-2011-1304: Pop-up block bypass via plug-ins. >Credit to Chamal De Silva.
• [Linux / Mac only] [70589] Medium CVE-2011-1305: Linked-list race in database handling. >Credit to Kostya Serebryany of the Chromium development community.
• [$500] [71586] Medium CVE-2011-1434: Lack of thread safety in MIME handling. >Credit to Aki Helin.
• [72523] Medium CVE-2011-1435: Bad extension with ‘tabs’ permission can capture local files. >Credit to Cole Snodgrass.
• [Linux only] [72910] Low CVE-2011-1436: Possible browser crash due to bad interaction with X. >Credit to miaubiz.
• [$1000] [73526] High CVE-2011-1437: Integer overflows in float rendering. >Credit to miaubiz.
• [$1000] [74653] High CVE-2011-1438: Same origin policy violation with blobs. >Credit to kuzzcc.
• [Linux only] [74763] High CVE-2011-1439: Prevent interference between renderer processes. >Credit to Julien Tinnes of the Google Security Team.
• [$1000] [75186] High CVE-2011-1440: Use-after-free with <ruby> tag and CSS. >Credit to Jose A. Vazquez.
• [$500] [75347] High CVE-2011-1441: Bad cast with floating select lists. >Credit to Michael Griffiths.
• [$1000] [75801] High CVE-2011-1442: Corrupt node trees with mutation events. >Credit to Sergey Glazunov and wushi of team 509.
• [$1000] [76001] High CVE-2011-1443: Stale pointers in layering code. >Credit to Martin Barbella.
• [$500] [Linux only] [76542] High CVE-2011-1444: Race condition in sandbox launcher. >Credit to Dan Rosenberg.
• [76646] Medium CVE-2011-1445: Out-of-bounds read in SVG. >Credit to wushi of team509.
• [$3000] [76666] [77507] [78031] High CVE-2011-1446: Possible URL bar spoofs with navigation errors and interrupted loads. >Credit to kuzzcc.
• [$1000] [76966] High CVE-2011-1447: Stale pointer in drop-down list handling. >Credit to miaubiz. 
• [$1000] [77130] High CVE-2011-1448: Stale pointer in height calculations. >Credit to wushi of team509.
• [$1000] [77346] High CVE-2011-1449: Use-after-free in WebSockets. >Credit to Marek Majkowski.
• [77349] Low CVE-2011-1450: Dangling pointers in file dialogs. >Credit to kuzzcc.
• [$2000] [77463] High CVE-2011-1451: Dangling pointers in DOM id map. >Credit to Sergey Glazunov.
• [$500] [77786] Medium CVE-2011-1452: URL bar spoof with redirect and manual reload. >Credit to Jordi Chancel.
• [$1500] [79199] High CVE-2011-1454: Use-after-free in DOM id handling. >Credit to Sergey Glazunov.
• [79361] Medium CVE-2011-1455: Out-of-bounds read with multipart-encoded PDF. >Credit to Eric Roman of the Chromium development community.
• [79364] High CVE-2011-1456: Stale pointers with PDF forms. >Credit to Eric Roman of the Chromium development community.

We would also like to thank miaubiz, kuzzcc, Slawomir Blazek, Drew Yao and Braden Thomas of Apple Product Security and Christian Hollier for working with us during the development cycle and helping prevent bugs from ever reaching the stable channel.

More on what's new at the Official Chrome Blog. You can find full details about the changes that are in Chrome 11 in the SVN revision log. If you find new issues, please let us know byfiling a bug. Want to change to another Chrome release channel? Find out how.