CVE-2017-0591 Memory corruption in Android

High 7.8 Published Updated

Remote attackers can execute arbitrary code via memory corruption in the Android Mediaserver component when processing crafted media files.

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-2017-0591?

CVE-2017-0591 is a high-severity memory corruption vulnerability in Google Android, published on 12 May 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 libavc in Mediaserver 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. Product: Android. Versions: 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2. Android ID: A-34097672.

Weakness: CWE-119

Which versions are affected by CVE-2017-0591?

It affects 1 product.

Products include Google Android.

How do I fix CVE-2017-0591?

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

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

All Google Android vulnerabilities

Sources

Also known as GHSA-h9cj-5pxp-v3gc, UBUNTU-CVE-2017-0591.

Is CVE-2017-0591 in your software?

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

Check your SBOMs for free