See the release notes at http://googlechromereleases.blogspot.com/2010/08/stable-channel-update_19.html Some details: [$1337] [45400] Critical Memory corruption with file dialog. Credit to Sergey Glazunov. [$500] [49596] High Memory corruption with SVGs. Credit to wushi of team509. [$500] [49628] High Bad cast with text editing. Credit to wushi of team509. [$1000] [49964] High Possible address bar spoofing with history bug. Credit to Mike Taylor. [$2000] [50515] [51835] High Memory corruption in MIME type handling. Credit to Sergey Glazunov. [$1337] [50553] Critical Crash on shutdown due to notifications bug. Credit to Sergey Glazunov. [51146] Medium Stop omnibox autosuggest if the user might be about to type a password. Credit to Robert Hansen. [$1000] [51654] High Memory corruption with Ruby support. Credit to kuzzcc. [$1000] [51670] High Memory corruption with Geolocation support. Credit to kuzzcc. You can read more about the severity ratings at http://sites.google.com/a/chromium.org/dev/developers/severity-guidelines . I suggest to rate it B2 on the Gentoo scale. Security, this bug sort of obsoletes bug #330003 (you now have 4 www-client/chromium bugs in the queue). Arches, please stabilize. A compile test and basic smoke test is sufficient. The 375 branch gets only the most important bugfixes.
x86 stable
amd64 done
Chromium Herd has nothing to do here. The vulnerable versions are no longer in the tree.
GLSA 201012-01, thanks everyone.
CVE-2010-3120 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-3120): Google Chrome before 5.0.375.127 does not properly implement the Geolocation feature, which allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via unknown vectors. CVE-2010-3119 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-3119): Google Chrome before 5.0.375.127 and webkitgtk before 1.2.6 do not properly support the Ruby language, which allows attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via unknown vectors. CVE-2010-3118 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-3118): The autosuggest feature in the Omnibox implementation in Google Chrome before 5.0.375.127 does not anticipate entry of passwords, which might allow remote attackers to obtain sensitive information by reading the network traffic generated by this feature. CVE-2010-3117 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-3117): Google Chrome before 5.0.375.127 does not properly implement the notifications feature, which allows remote attackers to cause a denial of service (application crash) and possibly have unspecified other impact via unknown vectors. CVE-2010-3116 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-3116): Multiple use-after-free vulnerabilities in WebKit, as used in Apple Safari before 4.1.3 and 5.0.x before 5.0.3, Google Chrome before 5.0.375.127, and webkitgtk before 1.2.6, allow remote attackers to execute arbitrary code or cause a denial of service (application crash) via vectors related to improper handling of MIME types by plug-ins. CVE-2010-3115 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-3115): Google Chrome before 5.0.375.127, and webkitgtk before 1.2.6, does not properly implement the history feature, which might allow remote attackers to spoof the address bar via unspecified vectors. CVE-2010-3114 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-3114): The text-editing implementation in Google Chrome before 5.0.375.127, and webkitgtk before 1.2.6, does not check a node type before performing a cast, which has unspecified impact and attack vectors related to (1) DeleteSelectionCommand.cpp, (2) InsertLineBreakCommand.cpp, or (3) InsertParagraphSeparatorCommand.cpp in WebCore/editing/. CVE-2010-3113 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-3113): Google Chrome before 5.0.375.127, and webkitgtk before 1.2.5, does not properly handle SVG documents, which allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via unknown vectors related to state changes when using DeleteButtonController. CVE-2010-3112 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-3112): Google Chrome before 5.0.375.127 does not properly implement file dialogs, which allows attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via unknown vectors.