CVE-2016-3820 Memory corruption in n/a

Critical 9.8 Published Updated

Remote attackers can execute arbitrary code or cause denial of service via crafted media files due to memory corruption in the Android H.264 decoder.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2016-3820?

CVE-2016-3820 is a critical memory corruption vulnerability in Google Android, published on 5 Aug 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

The ih264d decoder in mediaserver in Android 6.x before 2016-08-01 mishandles slice numbers, which allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted media file, aka internal bug 28673410.

Weakness: CWE-119

Which versions are affected by CVE-2016-3820?

It affects 1 product.

Products include Google Android.

How do I fix CVE-2016-3820?

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

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

All Google Android vulnerabilities

Sources

Also known as GHSA-pmx3-4h9r-qfpj, UBUNTU-CVE-2016-3820.

Is CVE-2016-3820 in your software?

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

Check your SBOMs for free