dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2016-10457

CRITICAL · 9.8 CVSS v3.0 Published 2018-04-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile and Snapdragon Wear MDM9206, MDM9607, MDM9650, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 430, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 810, SD 820, SD 835, and SDX20, app is requesting more permissions than required.

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

On affected Qualcomm Snapdragon chipsets and Snapdragon Wear devices with Android security patches before April 2018, the Android permission framework incorrectly grants applications more permissions than they actually request or require. This systemic over-privileging could allow malicious apps to access sensitive device capabilities they should not be entitled to.

MitigationApply the vendor security patch (April 2018 or later security patch level) to affected devices. For devices no longer receiving updates, consider replacement or implement application permission auditing and restriction at the EMM/MDM level.

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
Mdm9206 FirmwareOperating system
Affected:all versions
Mdm9607 FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions
Msm8909w FirmwareOperating system
Affected:all versions
Sd 210 FirmwareOperating system
Affected:all versions
Sd 212 FirmwareOperating system
Affected:all versions
Sd 205 FirmwareOperating system
Affected:all versions
Sd 400 FirmwareOperating system
Affected:all versions

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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. Identify the Qualcomm chipset model
    Check the device specifications or use commands like 'getprop ro.hardware' or 'cat /proc/cpuinfo' to identify the chipset. On Android, you can also check in Settings > About Phone > Hardware info
    Affected if The chipset matches one of the following: Mdm9206, Mdm9607, Mdm9650, Msm8909w, Sd 210, Sd 212, Sd 205, or Sd 400
  2. Check the Android security patch level
    On the Android device, go to Settings > Security > Security update, or use 'getprop ro.build.version.security_patch' via ADB shell. This displays the date of the installed security patch (format: YYYY-MM-DD)
    Affected if The security patch date is earlier than 2018-04-01 or the field is empty/unavailable, indicating no patch from April 2018 or later has been applied
  3. Verify the device is running Android
    Confirm the device runs the Android OS by checking 'getprop ro.build.version.sdk' or checking Settings > About Phone > Android version
    Affected if The device runs Android and meets both conditions above (affected chipset AND pre-April-2018 security patch)

The device is affected if it uses one of the listed Qualcomm Snapdragon chipsets and has a security patch level earlier than April 2018, as the permission framework bug exists in the firmware of these specific chipsets with older patch dates.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor security patch (April 2018 or later security patch level) to affected devices. For devices no longer receiving updates, consider replacement or implement application permission auditing and restriction at the EMM/MDM level.

Recommended fix High confidence

Android security patch level April 2018 or later (specific to device model and carrier)

  1. Verify the current Android security patch level on the affected device through Settings > About Phone > Security patch level
  2. Contact the device manufacturer (OEM) or mobile carrier to obtain a firmware update with Android security patch level April 2018 or later
  3. Apply the provided firmware update to the device to remediate the excessive permissions vulnerability
Caveat Update availability depends on OEM/carrier support; older devices may no longer receive updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-10457 — 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-10457 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