libxslt 1.1.26 and earlier, as used in Google Chrome before 21.0.1180.89, does not properly manage memory, which might allow remote attackers to cause a denial of service (application crash) via a crafted XSLT expression that is not properly identified during XPath navigation, related to (1) the xsltCompileLocationPathPattern function in libxslt/pattern.c and (2) the xsltGenerateIdFunction function in libxslt/functions.c.
https://chromiumcodereview.appspot.com/10830177
https://chromiumcodereview.appspot.com/10823168
http://www.mandriva.com/security/advisories?name=MDVSA-2012:164
http://www.debian.org/security/2012/dsa-2555
http://support.apple.com/kb/HT6001
http://support.apple.com/kb/HT5934
http://src.chromium.org/viewvc/chrome/trunk/src/third_party/libxslt/libxslt/pattern.c?view=log
http://src.chromium.org/viewvc/chrome/trunk/src/third_party/libxslt/libxslt/functions.c?view=log
http://secunia.com/advisories/54886
http://secunia.com/advisories/50838
http://lists.opensuse.org/opensuse-security-announce/2012-09/msg00030.html
http://lists.apple.com/archives/security-announce/2013/Sep/msg00006.html
http://lists.apple.com/archives/security-announce/2013/Oct/msg00009.html
http://googlechromereleases.blogspot.com/2012/08/stable-channel-update_30.html