dbcve.org
AndroidOperating system · Google

CVE-2016-3771

HIGH · 7.8 CVSS v3.0 Published 2016-07-11
Fix available
A fix is available. Upgrade to after 6.0.1 or later.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The MediaTek drivers in Android before 2016-07-05 on Android One devices allow attackers to gain privileges via a crafted application, aka Android internal bug 29007611 and MediaTek internal bug ALPS02703102.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Local privilege escalation vulnerability in MediaTek GPU/display drivers on Android One devices running Android versions before the July 5, 2016 security patch. A crafted malicious application can exploit improper access control in the MediaTek driver to gain elevated system privileges.

MitigationApply the July 2016 Android security patch or later, which contains the MediaTek driver fix (ALPS02703102). This is a system-level vendor patch; affected device users should ensure they receive official OTA updates from their device manufacturer.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AndroidOperating system
Affected:<= 6.0.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Android OS version
    Run 'getprop ro.build.version.release' in a terminal or check Settings > About Phone > Android version
    Affected if Version displays 6.0.1 or lower (6.0, 5.1, 5.0, etc.)
  2. Verify device uses MediaTek chipset
    Check if the device is an Android One device by running 'getprop ro.product.name' or inspecting the device specifications. Android One devices typically use MediaTek processors.
    Affected if Device is an Android One phone with MediaTek GPU/display driver
  3. Check security patch level
    Run 'getprop ro.build.version.security_patch' or go to Settings > About Phone > Security patch level
    Affected if Patch level shows a date before July 5, 2016 (e.g., June 1, 2016, May 2, 2016, etc.) or the field is empty/unavailable

A device is affected if it is an Android One device running Android 6.0.1 or earlier with a security patch level dated before July 5, 2016.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 6.0.1
Interim mitigation

Apply the July 2016 Android security patch or later, which contains the MediaTek driver fix (ALPS02703102). This is a system-level vendor patch; affected device users should ensure they receive official OTA updates from their device manufacturer.

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-3771 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-3771 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data