dbcve.org
Sd 410 FirmwareOperating system · Qualcomm

CVE-2016-10445

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 410/12, SD 425, SD 427, SD 430, SD 435, SD 450, SD 615/16/SD 415, SD 625, SD 820, SD 820A, SD 835, SD 845, SD 850, SDM630, SDM636, SDM660, and Snapdragon_High_Med_2016, input is not properly validated in a QTEE API function.

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 confidence

An input validation vulnerability exists in the Qualcomm Trusted Execution Environment (QTEE) API function across multiple Snapdragon mobile and automotive processors (SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 450, SD 615/16/SD 415, SD 625, SD 820, SD 820A, SD 835, SD 845, SD 850, SDM630, SDM636, SDM660). The lack of proper input validation in the QTEE API could allow an attacker to potentially execute code within the trusted execution environment or cause memory corruption.

MitigationApply Android security patches released April 5, 2018 or later, or update device firmware with the latest Qualcomm processor microcode/patch level. For end-of-life devices, consider replacement with supported hardware.

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 410 FirmwareOperating system
Affected:all versions
Sd 412 FirmwareOperating system
Affected:all versions
Sd 425 FirmwareOperating system
Affected:all versions
Sd 430 FirmwareOperating system
Affected:all versions
Sd 450 FirmwareOperating system
Affected:all versions
Sd 615 FirmwareOperating system
Affected:all versions
Sd 616 FirmwareOperating system
Affected:all versions
Sd 415 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 the device specifications or use commands like 'getprop' (Android) or check /proc/cpuinfo to find the processor identifier (e.g., MSM8916 for SD 410/12, MDM9607 for SD 615/16/415)
    Affected if The processor model matches one of the affected variants: SD 410, SD 412, SD 415, SD 425, SD 430, SD 450, SD 615, SD 616, or other Snapdragon variants listed in the CVE summary (SD 427, SD 435, SD 625, SD 820, SD 820A, SD 835, SD 845, SD 850, SDM630, SDM636, SDM660)
  2. Check the Android security patch level
    On Android devices, run 'getprop ro.build.version.security_patch' or check Settings > About Phone > Android security patch level
    Affected if The security patch level is earlier than April 5, 2018, indicating the device has not received the fix for this vulnerability
  3. Verify the baseband or firmware patch level
    Check Qualcomm firmware version using 'getprop' commands such as 'getprop vendor.qcom.version.release' or check the baseband version via 'getprop gsm.version.baseband'
    Affected if The firmware or baseband version does not reflect the April 2018 patch or later Qualcomm microcode updates
  4. Confirm QTEE is accessible and active
    This vulnerability requires the QTEE (Trusted Execution Environment) to be present and accessible. On Android, verify the presence of /dev/tee or /dev/tz entries in /dev/ which indicate an active TEE
    Affected if The device has an active TEE implementation (which most Snapdragon devices with this processor do have), making the input validation flaw potentially exploitable if unpatched

A device is affected if it contains a listed Snapdragon processor (SD 410/412/415/425/430/450/615/616 or variants from the summary) and has not received the April 5, 2018 Android security patch or later Qualcomm firmware update.

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 patches released April 5, 2018 or later, or update device firmware with the latest Qualcomm processor microcode/patch level. For end-of-life devices, consider replacement with supported hardware.

Recommended fix Moderate confidence

Android Security Patch Level 2018-04-05 or later (contact OEM for device-specific firmware)

  1. 1. Contact your device manufacturer (OEM) to obtain the latest Android security patch level for your device.
  2. 2. Request firmware updates specifically addressing the QTEE input validation vulnerability (CVE-2016-10445).
  3. 3. Apply the Android security patch level from April 2018 or later, as this vulnerability was addressed in the 2018-04-05 security patch level.
  4. 4. Verify the installed security patch level on your device via Settings > About Phone > Security Patch Level.
Caveat OEM-dependent; some older devices may not receive updates

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

Fix this in Sd 410 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing16.0 h
  • Review / QA8.0 h
36.0 hours of engineering $6,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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