<chromium-browser-20.0.1132.43: multiple vulnerabilities (CVE-2012-{2807,2815,2817,2818,2819,2820,2821,2823,2824,2825,2826,2829,2830,2831,2834})

Bug #1018204 reported by Karma Dorje
262
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Fix Released
Undecided
Unassigned
libxml2 (Debian)
Fix Released
Unknown
libxml2 (Fedora)
Fix Released
Medium
libxml2 (Ubuntu)
Fix Released
Undecided
Unassigned
libxslt (Debian)
Fix Released
Unknown
libxslt (Fedora)
Fix Released
Medium
libxslt (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

The Google Chrome team is happy to announce the arrival of Chrome 20 (20.0.1132.43) to the Stable Channel for Windows, Mac, Linux, and Chrome Frame. Release notes in URL [1].

[1] http://googlechromereleases.blogspot.com/2012/06/stable-channel-update_26.html

Karma Dorje (taaroa)
visibility: private → public
Revision history for this message
In , jlieskov (jlieskov-redhat-bugs) wrote :

Common Vulnerabilities and Exposures assigned an identifier CVE-2012-2807 to the following vulnerability:

Multiple integer overflows in libxml2, as used in Google Chrome before 20.0.1132.43, on 64-bit Linux platforms allow remote attackers to cause a denial of service or possibly have unspecified other impact via unknown vectors.

References:
[1] http://code.google.com/p/chromium/issues/detail?id=129930
[2] http://googlechromereleases.blogspot.com/2012/06/stable-channel-update_26.html

Karma Dorje (taaroa)
summary: <chromium-browser-20.0.1132.43: multiple vulnerabilities
- (CVE-2012-{2807,2815,2816,2817,2818,2819,2820,2821,2823,2824,2825,2826,2829,2830,2831,2834})
+ (CVE-2012-{2807,2815,2817,2818,2819,2820,2821,2823,2824,2825,2826,2829,2830,2831,2834})
Revision history for this message
In , Vincent (vincent-redhat-bugs) wrote :

The Google Chrome 20 release announcement [1] noted and fixed a flaw in libxslt:

* [$500] [127417] Medium CVE-2012-2825: Wild read in XSL handling. Credit to Nicholas Gregoire.

This has been corrected in the Chromium git repository [2]; the upstream fix is noted as pending.

[1] http://googlechromereleases.blogspot.de/2012/06/stable-channel-update_26.html
[2] http://git.chromium.org/gitweb/?p=chromium/src.git;a=patch;h=bb7bfb81c158268fb242292b7e0fbd2d3b933d09

Revision history for this message
In , Vincent (vincent-redhat-bugs) wrote :

Created libxslt tracking bugs for this issue

Affects: fedora-all [bug 835983]

Changed in libxml2 (Debian):
status: Unknown → Incomplete
Revision history for this message
In , jlieskov (jlieskov-redhat-bugs) wrote :
Revision history for this message
Tyler Hicks (tyhicks) wrote :

Marking the libxml2 task as confirmed since a CVE has been assigned. But it would be good to have more information on the vulnerability and to see some activity from upstream before we take action.

Changed in chromium-browser (Ubuntu):
status: New → Triaged
Tyler Hicks (tyhicks)
Changed in libxml2 (Ubuntu):
status: New → Confirmed
Changed in libxslt (Debian):
status: Unknown → New
Changed in libxslt (Debian):
status: New → Fix Released
Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. Since chromium-browser is in universe or multiverse, it is community maintained. If you are able, I suggest coordinating with upstream and posting a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures.

Changed in libxslt (Ubuntu):
status: New → Confirmed
Changed in libxml2 (Debian):
status: Incomplete → Confirmed
Revision history for this message
In , veillard (veillard-redhat-bugs) wrote :

Okay, i finally pushed a patch upstream that I think should backport
rather easily

http://git.gnome.org/browse/libxml2/commit/?id=459eeb9dc752d5185f57ff6b135027f11981a626

that one

http://git.gnome.org/browse/libxml2/commit/?id=4f9fdc709c4861c390cd84e2ed1fd878b3442e28

should also be applied in the errata to avoid similar problem elsewhere.
Somehow that's not a complete fix but that's the most immediate and
simple way to stop the given problem. I'm still working on a (rather
large and intrusive) set of patches for upstream but I would not suggest
to push that in RHEL. For fedora I may be tempted to rebase once a new
libxml2 version is out

Daniel

Revision history for this message
In , huzaifas (huzaifas-redhat-bugs) wrote :

The above patches, described in comment #4 seems to solve the problem here. libxml2 no longer crashes with them.

For Red Hat Enterprise Linux use case, we may however require few more patches from upstream.

Revision history for this message
In , huzaifas (huzaifas-redhat-bugs) wrote :

Created libxml2 tracking bugs for this issue

Affects: fedora-all [bug 843743]

Changed in libxml2 (Debian):
status: Confirmed → Fix Released
Revision history for this message
In , teger (teger-redhat-bugs) wrote :

This has been reported over 2 months ago with a possible fix coming in a little over a month. Is there any plan of action to fix libxml2 vulnerabilities?

Primarily this is a bump to put in back on someones to do list.
Thank you

Revision history for this message
In , errata-xmlrpc (errata-xmlrpc-redhat-bugs) wrote :

This issue has been addressed in following products:

  Red Hat Enterprise Linux 6
  Red Hat Enterprise Linux 5

Via RHSA-2012:1265 https://rhn.redhat.com/errata/RHSA-2012-1265.html

Revision history for this message
In , errata-xmlrpc (errata-xmlrpc-redhat-bugs) wrote :

This issue has been addressed in following products:

  Red Hat Enterprise Linux 5
  Red Hat Enterprise Linux 6

Via RHSA-2012:1288 https://rhn.redhat.com/errata/RHSA-2012-1288.html

Revision history for this message
In , huzaifas (huzaifas-redhat-bugs) wrote :

Created mingw32-libxml2 tracking bugs for this issue

Affects: epel-5 [bug 858914]
Affects: fedora-all [bug 858915]

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

libxslt-1.1.26-10.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

libxslt-1.1.26-9.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

libxslt-1.1.27-2.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.

Revision history for this message
In , huzaifas (huzaifas-redhat-bugs) wrote :

This flaw affects x86_64 version of libxml2 only, however mingw32-libxml2 is only shipped as x86 (32-bit) and therefore it is not affected.

Statement:

This issue affected the version of libxml2 as shipped with Red Hat Enterprise Linux 5 and 6 has been addressed via RHSA-2012:1288. This issue does not affect the version of mingw32-libxml2 as shipped with Red Hat Enterprise Linux 6.

Chad Miller (cmiller)
Changed in chromium-browser (Ubuntu):
status: Triaged → Fix Released
Changed in libxml2 (Ubuntu):
status: Confirmed → Fix Released
Changed in libxslt (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
In , Vincent (vincent-redhat-bugs) wrote :

Statement:

(none)

Changed in libxml2 (Fedora):
importance: Unknown → Medium
status: Unknown → Confirmed
Changed in libxslt (Fedora):
importance: Unknown → Medium
status: Unknown → Fix Released
Changed in libxml2 (Fedora):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public Security information  
Everyone can see this security related information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.