From redhat bugzilla at $URL: A heap-based buffer overflow was found in the way libxml2 decoded an entity reference with a long name. A remote attacker could provide a specially-crafted XML file, which once opened in an application linked against libxml would cause that application to crash, or, potentially, execute arbitrary code with the privileges of the user running the application. Reference: http://googlechromereleases.blogspot.com/2012/01/stable-channel-update.html Patch: http://git.gnome.org/browse/libxml2/commit/?id=5bd3c061823a8499b27422aee04ea20aae24f03e
Fixed in libxml2-2.7.8-r4, thanks for reporting! >*libxml2-2.7.8-r4 (10 Jan 2012) > > 10 Jan 2012; Alexandre Rostovtsev <tetromino@gentoo.org> > +libxml2-2.7.8-r4.ebuild, > +files/libxml2-2.7.8-allocation-error-copying-entities.patch: > Fix heap-based overflow in parsing long entity references (CVE-2011-3919, bug > #398361, thanks to Agostino Sarubbo for reporting).
(In reply to comment #1) > Fixed in libxml2-2.7.8-r4, thanks for reporting! > Great, thank you. Arches, please test and mark stable: =dev-libs/libxml2-2.7.8-r4 Target keywords : "alpha amd64 arm hppa ia64 m68k ppc ppc64 s390 sh sparc x86"
amd64 stable
ppc/ppc64 done
x86 stable
alpha/arm/ia64/m68k/s390/sh/sparc stable
Stable for HPPA.
Filed new request in glsamaker.
CVE-2011-3919 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-3919): Heap-based buffer overflow in libxml2, as used in Google Chrome before 16.0.912.75, allows remote attackers to cause a denial of service or possibly have unspecified other impact via unknown vectors.
This issue was resolved and addressed in GLSA 201202-09 at http://security.gentoo.org/glsa/glsa-201202-09.xml by GLSA coordinator Sean Amoss (ackle).