dbcve.org
Sd 210 FirmwareOperating system · Qualcomm

CVE-2016-10467

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 210/SD 212/SD 205, SD 400, SD 410/12, SD 615/16/SD 415, SD 617, SD 650/52, SD 800, SD 808, SD 820, and SD 820A, function ce_pkcs1_pss_padding_verify_auto_recover_saltlen assumes that the size of the encoded message is equal to the size of the RSA modulus. This assumption is true for most RSA keys, but it fails when modulus_bitlen % 8 == 1.

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

Vulnerability in Qualcomm Snapdragon Cryptography Engine's RSA PKCS#1 PSS padding verification function. The function incorrectly assumes encoded message size equals RSA modulus size, which fails for keys where modulus_bitlen % 8 == 1, potentially allowing signature verification bypass.

MitigationApply Android security patch level 2018-04-05 or later for affected Qualcomm Snapdragon devices (SD 210/212/205, SD 400, SD 410/12, SD 615/16/415, SD 617, SD 650/52, SD 800, SD 808, SD 820, SD 820A). This is a vendor-supplied firmware update requiring OEM distribution.

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 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
Sd 410 FirmwareOperating system
Affected:all versions
Sd 412 FirmwareOperating system
Affected:all versions
Sd 615 FirmwareOperating system
Affected:all versions
Sd 616 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, system information, or boot logs to determine the exact Snapdragon variant (Sd 210, Sd 212, Sd 205, Sd 400, Sd 410, Sd 412, Sd 615, or Sd 616)
    Affected if The device uses any of the affected Snapdragon variants (Sd 210, Sd 212, Sd 205, Sd 400, Sd 410, Sd 412, Sd 615, or Sd 616)
  2. Confirm RSA PSS signature verification is in use
    Review application or system code that performs cryptographic signature verification to determine if PKCS#1 PSS padding scheme is being used
    Affected if RSA PSS padding is used for signature verification in any security-critical function on the affected device
  3. Identify RSA key modulus bit length
    Examine the RSA public or private key in use and determine the exact bit length of the modulus (e.g., 1025, 2049, 4097 bits)
    Affected if The RSA key modulus bit length satisfies (modulus_bitlen % 8) == 1 (e.g., 1025, 2049, 4097 bits)
  4. Check firmware patch level
    On Android devices, verify the security patch level in Settings > About Phone > Android security patch level
    Affected if The security patch level is earlier than 2018-04-05 and the device uses an affected Snapdragon variant with RSA PSS verification

You are affected if your device uses any of the listed Snapdragon variants (Sd 210/212/205/400/410/412/615/616) with all firmware versions, uses RSA PSS signature verification, and employs RSA keys with bit length where (modulus_bitlen % 8) equals 1, and the Android security patch is pre-2018-04-05.

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 for affected Qualcomm Snapdragon devices (SD 210/212/205, SD 400, SD 410/12, SD 615/16/415, SD 617, SD 650/52, SD 800, SD 808, SD 820, SD 820A). This is a vendor-supplied firmware update requiring OEM distribution.

Recommended fix Moderate confidence

Android Security Patch Level 2018-04-05 or later (for SD 210/212/205/400/410/412/615/616)

  1. Check current Android security patch level on the device (Settings > About Phone > Security patch level)
  2. Update to Android with security patch level 2018-04-05 or later
  3. If no update available from device manufacturer, contact the device OEM for firmware updates addressing this vulnerability
Caveat Standard security update with no expected compatibility issues; update includes fixes for this RSA padding verification bypass

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

Fix this in Sd 210 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
16.0 hours of engineering $2,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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