CVE-2016-6701 Memory corruption in Android

High 7.8 Published Updated

Remote attackers can execute arbitrary code in the gallery process via a crafted file causing memory corruption in libskia.

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-6701?

CVE-2016-6701 is a high-severity memory corruption vulnerability in Google Android, published on 25 Nov 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 libskia 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 High due to the possibility of remote code execution within the context of the gallery process. Android ID: A-30190637.

Weakness: CWE-284, CWE-119

Which versions are affected by CVE-2016-6701?

It affects 1 product.

Products include Google Android.

How do I fix CVE-2016-6701?

No fix has been published for CVE-2016-6701 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-6701 being exploited?

There is no known exploitation of CVE-2016-6701 in the wild and no public exploit code.

All Google Android vulnerabilities

Sources

Also known as GHSA-7q83-f9g2-964w, UBUNTU-CVE-2016-6701.

Is CVE-2016-6701 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free