CVE-2016-6710
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 · uneditedAn information disclosure vulnerability in the download manager in Android 5.0.x before 5.0.2, 5.1.x before 5.1.1, 6.x before 2016-11-01, and 7.0 before 2016-11-01 could enable a local malicious application to bypass operating system protections that isolate application data from other applications. This issue is rated as High because it could be used to gain access to data that the application does not have access to. Android ID: A-30537115.
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 · moderate confidenceAn information disclosure vulnerability in Android's Download Manager allows a local malicious application to bypass OS sandbox protections that isolate application data, potentially enabling access to data the attacking app normally wouldn't have permission to access. The vulnerability exists across Android 5.0.x through 7.0 before November 2016 security patches.
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>= 5.0, < 5.0.2>= 5.1, < 5.1.1>= 6.0, <= 6.0.1= 7.0CVSS 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
- None
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Check the Android OS versionGo to Settings > About Phone (or About Device) > Android version. Alternatively, run 'getprop ro.build.version.release' via ADB shell.Affected if The version is 5.0, 5.0.1, 5.1, 5.1.1, 6.0, 6.0.1, or 7.0 (these fall within the affected ranges)
-
Check the security patch levelGo to Settings > About Phone > Security patch level. Alternatively, run 'getprop ro.build.version.security_patch' via ADB shell.Affected if The patch level is earlier than November 2016 or the field is empty/unavailable (the fix was released in the November 2016 security update)
-
Confirm the Download Manager component is presentCheck if the com.android.providers.downloads provider is installed. Run 'pm list packages | grep download' via ADB shell or inspect the system app list.Affected if The Download Manager package exists on the device (this is the vulnerable component)
-
Verify patch application statusCross-reference the device's security patch level against Google's Android Security Bulletin for November 2016. Confirm whether the device manufacturer has released and applied this specific update.Affected if The November 2016 security update has not been applied to the device
A device is affected if it runs Android 5.0.x through 7.0 AND has not received the November 2016 security patch level update.
Generated from the published advisory. Verify against your own configuration.
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 data5.0.25.1.1
Apply Android platform security updates dated November 2016 or later to affected devices. For enterprise environments, ensure mobile device management policies enforce OS patch levels meeting this baseline.
- Consultation8.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-6710 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-6710 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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