LiveActive security incident?Get immediate response
CVE Record

CVE-2016-10467: In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile and Snapdrag...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This CVE concerns older Android builds on specific Qualcomm Snapdragon mobile and automotive chips. A Qualcomm cryptographic padding verification function made an unsafe size assumption for rare RSA key shapes. The public sources identify affected chipsets and the Android patch level, but do not state business impact, CVSS severity, or active exploitation. Likely exposure is legacy Android or embedded automotive devices using the named Qualcomm Snapdragon platforms with security patch levels before 2018-04-05. Modern supported devices should be checked by patch level and OEM firmware status, not chipset name alone. Set priority based on asset sensitivity and whether affected legacy devices remain in production. The age of the issue lowers urgency for fully patched fleets, but unsupported mobile or automotive endpoints should be tracked and remediated. Mitigation focus: Update affected devices to Android security patch level 2018-04-05 or later.; Check OEM firmware bulletins for Qualcomm-specific fixes and supported builds.; Prioritize unsupported devices for replacement or compensating controls..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2016-10467 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Qualcomm, Inc.Snapdragon Automobile, Snapdragon MobileSD 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, SD 820AListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.