CVE-2017-0663 Memory corruption in Android
Remote attackers can execute arbitrary code in Android via a crafted file exploiting a memory corruption flaw in libxml2.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2017-0663?
CVE-2017-0663 is a high-severity memory corruption vulnerability in Google Android, published on 14 Jun 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Official description
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.
Weakness: CWE-787
Which versions are affected by CVE-2017-0663?
It affects 1 product.
Products include Google Android.
How do I fix CVE-2017-0663?
Apply the vendor's patch.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2017-0663 being exploited?
There is no known exploitation of CVE-2017-0663 in the wild and no public exploit code.
Other vulnerabilities in Google Android
Sources
Also known as DEBIAN-CVE-2017-0663, ECHO-d74a-1a43-82c4, GHSA-9cf7-h7g3-cg3p, UBUNTU-CVE-2017-0663.