dbcve.org
Sd 425 FirmwareOperating system · Qualcomm

CVE-2016-10430

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 Automobile and Snapdragon Mobile SD 425, SD 430, SD 450, SD 625, SD 650/52, SD 820, and SD 820A, when executing a TA which has been granted privileges to the CPVC MINK class it is possible for the TA to access methods exposed by the CPVC interface.

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

In Qualcomm Snapdragon processors (SD 425, 430, 450, 625, 650/52, 820, 820A), a Trusted Application (TA) granted privileges to the CPVC MINK class can improperly access methods exposed by the CPVC interface. This is a privilege escalation vulnerability in the Trusted Execution Environment (TEE) where authorization controls for the CPVC MINK class are insufficient, allowing a privileged TA to access restricted interface methods.

MitigationApply Android security patch level 2018-04-05 or later, which contains the vendor fix for this TEE authorization flaw. Organizations should inventory affected devices and ensure deployment of the appropriate Qualcomm firmware and Android security updates.

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
Sd 425 FirmwareOperating system
Affected:all versions
Sd 430 FirmwareOperating system
Affected:all versions
Sd 450 FirmwareOperating system
Affected:all versions
Sd 625 FirmwareOperating system
Affected:all versions
Sd 650 FirmwareOperating system
Affected:all versions
Sd 652 FirmwareOperating system
Affected:all versions
Sd 820a FirmwareOperating system
Affected:all versions
Sd 820 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 Snapdragon processor model
    Check /proc/cpuinfo or device settings under 'About Phone' > 'Processor' or 'Chipset' to determine if the device uses SD 425, 430, 450, 625, 650, 652, 820, or 820A
    Affected if The processor model matches any of the affected Snapdragon variants (SD 425, 430, 450, 625, 650, 652, 820, 820A)
  2. Verify the Android security patch level
    Navigate to Settings > About Phone > Android Version or check the Build Number to find the security patch level date
    Affected if The installed Android security patch level is earlier than 2018-04-05, meaning the TEE authorization fix has not been applied
  3. Check the baseband firmware version
    Look in Settings > About Phone > Baseband version or use 'getprop' command via ADB to retrieve the radio firmware version
    Affected if The device runs any firmware version on the affected Snapdragon models without the vendor fix applied
  4. Confirm TEE is present and accessible
    Check device documentation or use diagnostic tools to verify the Trusted Execution Environment is active; the vulnerability exists within the TEE CPVC MINK class authorization
    Affected if The device implements a TEE with CPVC MINK class access and the security patch level is pre-2018-04-05

A device is affected if it uses any of the listed Snapdragon processors (SD 425, 430, 450, 625, 650, 652, 820, 820A) and has not received the Android security patch level 2018-04-05 or later that contains the TEE authorization fix.

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 Android security patch level 2018-04-05 or later, which contains the vendor fix for this TEE authorization flaw. Organizations should inventory affected devices and ensure deployment of the appropriate Qualcomm firmware and Android security updates.

Recommended fix High confidence

Android security patch level April 2018 (2018-04-05) or later

  1. Check the current Android security patch level on the device (Settings > About Phone > Android security patch level)
  2. Update the device to the latest available Android security patch level from the device manufacturer
  3. Ensure the security patch level is dated 2018-04-05 or later to address this vulnerability
  4. If the device manufacturer has not released a security update containing the April 2018 patch level, contact the device manufacturer for support or consider upgrading to a device that receives regular monthly security updates

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

Fix this in Sd 425 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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