CVE-2016-10433
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 · uneditedIn Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile, Snapdragon Mobile, and Snapdragon Wear MDM9635M, MDM9640, MDM9645, 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 820, and SD 820A, TOCTOU vulnerability during SSD image decryption may cause memory corruption.
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 confidenceTOCTOU (Time-Of-Check-Time-Of-Use) vulnerability in the SSD image decryption process on Qualcomm Snapdragon chipsets (MDM9635M through SD 820A). The vulnerability exists in the race condition window between verifying SSD image integrity and actually using the decrypted image, potentially allowing memory corruption during the decryption process.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Qualcomm chipset modelCheck the device specifications, system information, or boot logs for the chipset identifier (e.g., MDM9635M, MDM9640, MDM9645, MSM8909W, SD210, SD212, SD205, SD400)Affected if The chipset matches any of the following: MDM9635M, MDM9640, MDM9645, MSM8909W, SD210, SD212, SD205, or SD400
-
Verify the firmware versionQuery the device firmware or boot logs for the specific firmware version string associated with the identified chipsetAffected if The firmware version is present (all versions of the affected chipsets are vulnerable)
-
Confirm SSD image decryption is in useInspect system or kernel logs for SSD image decryption operations, or check if the device performs encrypted SSD image loading during bootAffected if The device performs SSD image decryption operations during the boot process
-
Check the Android security patch levelOn Android devices, go to Settings > About Phone > Security Patch Level, or run 'getprop ro.build.version.security_patch'Affected if The security patch level is earlier than April 2018 (devices with earlier patches are likely vulnerable)
The device is affected if it uses one of the listed Qualcomm chipsets (MDM9635M, MDM9640, MDM9645, MSM8909W, SD210, SD212, SD205, SD400) and has a security patch level earlier than April 2018.
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 dataApply the April 2018 or later Android security patch level, which contains the fix for this vulnerability. For embedded/IoT devices, obtain and apply the vendor-specific firmware update from the device manufacturer that addresses this Qualcomm chipset vulnerability.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.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 $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10433 — 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-10433 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