CVE-2016-6699 Memory corruption in n/a
Remote attackers can execute arbitrary code via memory corruption in Android's Mediaserver by using a specially crafted media file.
- 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
- None listed
What is CVE-2016-6699?
CVE-2016-6699 is a high-severity memory corruption vulnerability in Google Android, published on 13 Dec 2016. 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 libstagefright in Mediaserver in Android 7.0 before 2016-11-01 could enable an attacker using a specially crafted file to cause memory corruption during media file and data processing. This issue is rated as Critical due to the possibility of remote code execution within the context of the Mediaserver process. Android ID: A-31373622.
Weakness: CWE-119
Which versions are affected by CVE-2016-6699?
It affects 1 product.
Products include Google Android.
How do I fix CVE-2016-6699?
No fix has been published for CVE-2016-6699 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2016-6699 being exploited?
There is no known exploitation of CVE-2016-6699 in the wild and no public exploit code.
Other vulnerabilities in Google Android
Sources
Also known as GHSA-6f4r-qfp6-6mf7, UBUNTU-CVE-2016-6699.