CVE-2016-3627: Input Validation
A vulnerability was found in a way libxml2 parses certain files. With the libxml2 in recovery mode, a maliciously crafted filed could cause libxml2 to crash.
References:
http://seclists.org/oss-sec/2016/q1/682
CVE assignment:
http://seclists.org/oss-sec/2016/q1/683
Other sources
Missing recursive loop detection checks were found in the xmlParserEntityCheck() and xmlStringGetNodeList() functions of libxml2, causing application using the library to crash by stack exhaustion while building the associated data. An attacker able to send XML data to be parsed in recovery mode could launch a Denial of Service on the application.
The xmlStringGetNodeList function in tree.c in libxml2 2.9.3 and earlier, when used in recovery mode, allows context-dependent attackers to cause a denial of service (infinite recursion, stack consumption, and application crash) via a crafted XML document.
Affected Software
Remediation
Patch Available
Patch Available
Event History
Parent advisories
This vulnerability appears in the following advisories.
Frequently Asked Questions
What is the severity of CVE-2016-3627?
CVE-2016-3627 is classified as a moderate severity vulnerability.
How do I fix CVE-2016-3627?
To fix CVE-2016-3627, update your libxml2 package to a version that includes the security patch.
Which versions of libxml2 are affected by CVE-2016-3627?
CVE-2016-3627 affects libxml2 versions prior to 0:2.7.6-21.el6_8.1 and 0:2.9.1-6.el7_2.3, among others.
What kind of attack does CVE-2016-3627 facilitate?
CVE-2016-3627 can be exploited to cause a denial of service via a crash of the libxml2 parser.
Is there a mitigation for CVE-2016-3627 if I cannot update?
If you cannot update, consider disabling recovery mode in libxml2 to mitigate the risk associated with CVE-2016-3627.