libxml2 through 2.9.1 does not properly handle external entities expansion unless an application developer uses the xmlSAX2ResolveEntity or xmlSetExternalEntityLoader function, which allows remote attackers to cause a denial of service (resource consumption), send HTTP requests to intranet servers, or read arbitrary files via a crafted XML document, aka an XML External Entity (XXE) issue. NOTE: it could be argued that because libxml2 already provides the ability to disable external entity expansion, the responsibility for resolving this issue lies with application developers; according to this argument, this entry should be REJECTed and each affected application would need its own CVE.
http://lists.opensuse.org/opensuse-security-announce/2013-11/msg00002.html
http://openwall.com/lists/oss-security/2013/02/21/24
http://openwall.com/lists/oss-security/2013/02/22/3
https://bugzilla.redhat.com/show_bug.cgi?id=915149
http://seclists.org/oss-sec/2013/q4/182
http://seclists.org/oss-sec/2013/q4/184
http://seclists.org/oss-sec/2013/q4/188
http://secunia.com/advisories/52662
http://secunia.com/advisories/54172
http://secunia.com/advisories/55568
https://git.gnome.org/browse/libxml2/commit/?id=4629ee02ac649c27f9c0cf98ba017c6b5526070f
http://www.debian.org/security/2013/dsa-2652
http://www.openwall.com/lists/oss-security/2013/04/12/6