Sd 410 FirmwareOperating system · Qualcomm

CVE-2016-10452

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

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 430, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 808, SD 810, SD 820, SD 820A, and SD 835, memory protection assertion happens after invoking TA termination out of order.

Technical summary

dbcve analysis · high confidence

A memory protection assertion failure occurs in Qualcomm Snapdragon TrustZone after a Trusted Application (TA) is terminated out of order, potentially allowing privilege escalation or memory corruption in the trusted execution environment.

MitigationApply Android security patch level 2018-04-05 or later, which contains the vendor fix for this TrustZone vulnerability. Users should ensure their device receives monthly security updates from their OEM.

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

Affected products & versions

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

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?

dbcve checks

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

Identify the Snapdragon chipset model

Check your device specifications or use a system info app to identify the exact Snapdragon processor model (e.g., Sd 410, Sd 412, Sd 425, Sd 430, Sd 450, Sd 615, Sd 616, Sd 415)

Affected if The device uses any of the following chipsets: Sd 410, Sd 412, Sd 425, Sd 430, Sd 450, Sd 615, Sd 616, or Sd 415
Verify the firmware version

Check the baseband or modem firmware version in your device settings under About Phone > Baseband version or through diagnostic tools like *#*#4636#*#* on Android

Affected if The firmware version corresponds to any version of the affected Snapdragon chipsets listed above (all versions are affected)
Check the Android security patch level

Go to Settings > About Phone > Android security patch level or Settings > Security > Security patch level to view the installed security update date

Affected if The security patch level is earlier than April 5, 2018 (2018-04-05) or if the patch level cannot be verified or is unknown
Confirm TrustZone/TEE status

Verify that the Trusted Execution Environment (TEE) is active on the device by checking for TEE-related services in /proc/tee_info or using diagnostic apps that report TEE status

Affected if The TEE/TrustZone is enabled and the device contains an affected Snapdragon chipset with pre-April 2018 firmware
Review OEM update status

Check with your device manufacturer (OEM) to confirm whether your specific device model has received the 2018-04-05 or later Android security update

Affected if The OEM has not released or applied the April 2018 security patch to your device model

You are affected if your device uses any of the listed Snapdragon chipsets (Sd 410/412/425/430/450/615/616/415) and the Android security patch level is earlier than 2018-04-05 or cannot be confirmed as updated.

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

Remediation

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 TrustZone vulnerability. Users should ensure their device receives monthly security updates from their OEM.

Recommended fix High confidence

Android with 2018-04-05 security patch level or later (or manufacturer-specific firmware incorporating the April 2018 Android security updates)

Check the current Android security patch level on the device via Settings > About Phone > Android security patch level
Update the device to an Android version with the 2018-04-05 security patch level or later
If the device manufacturer no longer provides updates, consider upgrading to a device that receives regular security patches
For embedded/IoT devices using these Snapdragon modules, contact the device manufacturer for firmware updates addressing this vulnerability

Caveat Ensure device compatibility and backup data before performing major Android updates; some older devices may not receive the update if the manufacturer has discontinued support

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

Fix this in Sd 410 Firmware Scoped from the published advisory

Consultation4.0 h
Implementation2.0 h
Testing8.0 h
Review / QA4.0 h

18.0 hours of engineering $3,080

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

source.android.comVendor Advisory
www.securityfocus.comThird Party AdvisoryVDB Entry
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2016-10452?

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.

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

At a glance

A fix existsA vendor remedy is published

Severity 9.8 Critical

Exploit likelihood EPSS, next 30 days 1.3%

Affects: Sd 410 Firmware

Remediation

A high-priority fix

Fix this in Sd 410 Firmware 18 hrs · High

Typical engagement from $3,080

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2016-10452 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References