CVE-2017-0663: Buffer Overflow
A heap-based buffer overflow vulnerability in libxml2 in xmlValidateOneNamespace function due to incorrect casting was found.
Upstream bug (private at this moment):
https://bugzilla.gnome.org/showbug.cgi?id=780228
Oss-fuzz bug report:
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=598
Android patch:
https://android.googlesource.com/platform/external/libxml2/+/521b88fbb6d18312923f0df653d045384b500ffc
References:
https://source.android.com/security/bulletin/2017-06-01#libraries
Other sources
A remote code execution vulnerability in libxml2 could enable an attacker using a specially crafted file to execute arbitrary code within the context of an unprivileged process. This issue is rated as High due to the possibility of remote code execution in an application that uses this library. Product: Android. Versions: 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2. Android ID: A-37104170.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
redhat/libxmlto a version that resolves this vulnerability.Fixed in 2.9.5 - Upgrade
Upgrade
debian/libxml2to a version that resolves this vulnerability.Fixed in 2.9.4+dfsg1-7+deb10u4Fixed in 2.9.4+dfsg1-7+deb10u6Fixed in 2.9.10+dfsg-6.7+deb11u4Fixed in 2.9.14+dfsg-1.3~deb12u1Fixed in 2.9.14+dfsg-1.3
Event History
Frequently Asked Questions
What is the severity of CVE-2017-0663?
CVE-2017-0663 is classified as a high severity vulnerability due to its potential for exploitation via a heap-based buffer overflow.
How do I fix CVE-2017-0663?
To fix CVE-2017-0663, upgrade to the latest version of libxml2 or libxml that addresses the vulnerability.
Which systems are affected by CVE-2017-0663?
CVE-2017-0663 affects various versions of libxml2, libxml on Red Hat, and multiple versions of Android.
What is the nature of the vulnerability in CVE-2017-0663?
CVE-2017-0663 involves a heap-based buffer overflow caused by incorrect casting in the xmlValidateOneNamespace function.
Is there a known exploit for CVE-2017-0663?
As of now, there are no public exploits reported for CVE-2017-0663, but it remains a serious concern.