CVE-2016-3863 Memory corruption in n/a

High 7.8 Published Updated

Remote attackers can execute arbitrary code on Android devices by exploiting stack-based buffer overflows in the media framework via crafted 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-2016-3863?

CVE-2016-3863 is a high-severity memory corruption vulnerability in Google Android, published on 11 Sep 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

Multiple stack-based buffer overflows in the AVCC reassembly implementation in Utils.cpp in libstagefright in MediaMuxer in Android 4.x before 4.4.4, 5.0.x before 5.0.2, 5.1.x before 5.1.1, 6.x before 2016-09-01, and 7.0 before 2016-09-01 allow remote attackers to execute arbitrary code via a crafted media file, aka internal bug 29161888.

Weakness: CWE-284

Which versions are affected by CVE-2016-3863?

It affects 1 product.

Products include Google Android.

How do I fix CVE-2016-3863?

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

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

All Google Android vulnerabilities

Sources

Also known as GHSA-6427-rmfx-x2xr, UBUNTU-CVE-2016-3863.

Is CVE-2016-3863 in your software?

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

Check your SBOMs for free