Upstream has released version 32.0.1700.77 on January 14: http://googlechromereleases.blogspot.com/2014/01/stable-channel-update.html This fixes a handful of new security issues. This is the current version in the stable channel: http://googlechromereleases.blogspot.com/search/label/Stable%20updates Reproducible: Steps to Reproduce:
Upstream has released version 32.0.1700.102 on January 27: http://googlechromereleases.blogspot.com/2014/01/stable-channel-update_27.html It fixes some regressions in the previous version and two security issues.
Updated packages uploaded for Mageia 3, Mageia 4, and Cauldron. Note to QA: there are both core and tainted builds for this package. Advisory: ======================== Use-after-free related to forms (CVE-2013-6641). Unprompted sync with an attackerâs Google account (CVE-2013-6643). Various fixes from internal audits, fuzzing and other initiatives (CVE-2013-6644). Use-after-free related to speech input elements (CVE-2013-6645). Use-after-free in web workers (CVE-2013-6646). Use-after-free in SVG images (CVE-2013-6649). Memory corruption in v8 before version 3.22.24.16 (CVE-2013-6650). References: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-6641 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-6643 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-6644 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-6645 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-6646 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-6649 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-6650 http://googlechromereleases.blogspot.com/2014/01/stable-channel-update.html http://googlechromereleases.blogspot.com/2014/01/stable-channel-update_27.html ======================== Updated packages in core/updates_testing: ======================== chromium-browser-stable-32.0.1700.102-1.mga3 chromium-browser-32.0.1700.102-1.mga3 chromium-browser-stable-32.0.1700.102-1.mga4 chromium-browser-32.0.1700.102-1.mga4 Updated packages in tainted/updates_testing: ======================== chromium-browser-stable-32.0.1700.102-1.mga3 chromium-browser-32.0.1700.102-1.mga3 chromium-browser-stable-32.0.1700.102-1.mga4 chromium-browser-32.0.1700.102-1.mga4 from SRPMS: chromium-browser-stable-32.0.1700.102-1.mga3.src.rpm chromium-browser-stable-32.0.1700.102-1.mga4.src.rpm
There are actually tainted srpms too so.. chromium-browser-stable-32.0.1700.102-1.mga3.src.rpm chromium-browser-stable-32.0.1700.102-1.mga4.src.rpm chromium-browser-stable-32.0.1700.102-1.mga3.tainted.src.rpm chromium-browser-stable-32.0.1700.102-1.mga4.tainted.src.rpm
tested mga3-64, core and tainted. Browsed various websites, tested javascript with sunspider, java with javatester.org, flash with youtube and a flash game. In tainted tested an mp3 from https://archive.org/details/testmp3testfile All OK.
Mga4-32 tested as above, all OK
Tested mga4-64, Testing complete for chromium-browser-stable-32.0.1700.102-1.mga4, nothing to report.
Tested mga3-32 as in comment 4, all OK. Update just needs the advisory update for validation.
the advisory of comment #2 is not enough ?
Yes, he's referring to me needing to add it to svn. Thanks Bill!
and David
Advisory uploaded. Validating Could sysadmin please push from 3&4 core & tainted updates_testing to updates Thanks!
Update pushed: http://advisories.mageia.org/MGASA-2014-0037.html
Debian has issued an advisory for this on February 16: http://www.debian.org/security/2014/dsa-2862