CVE-2012-5134: Buffer Overflow
A heap-buffer overflow was found in the way libxml2 decoded certain XML entitites. 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.in/2012/11/stable-channel-update.html
Patch: http://git.gnome.org/browse/libxml2/commit/?id=6a36fbe3b3e001a8a840b5c1fdd81cefc9947f0d
Other sources
Heap-based buffer underflow in the xmlParseAttValueComplex function in parser.c in libxml2 2.9.0 and earlier, as used in Google Chrome before 23.0.1271.91 and other products, allows remote attackers to cause a denial of service or possibly execute arbitrary code via crafted entities in an XML document.
— MITRE
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2012-5134?
CVE-2012-5134 has a severity rating that allows remote attackers to cause a denial of service or potentially execute arbitrary code.
How do I fix CVE-2012-5134?
To fix CVE-2012-5134, update your affected software to the latest versions of Google Chrome or libxml2, which include patches.
Which versions of Google Chrome are affected by CVE-2012-5134?
CVE-2012-5134 affects Google Chrome versions prior to 23.0.1271.91.
Is libxml2 vulnerable to CVE-2012-5134?
Yes, libxml2 versions up to and including 2.9.0 are vulnerable to CVE-2012-5134.
What specific function is responsible for the vulnerability in CVE-2012-5134?
The vulnerability in CVE-2012-5134 is caused by a heap-based buffer underflow in the xmlParseAttValueComplex function.