LiveActive security incident?Get immediate response
CVE Record

CVE-2016-10414: In Android before 2018-04-05 or earlier security patch level on Qualcomm Small Cell SoC, Snapdragon Automob...

In Android before 2018-04-05 or earlier security patch level on Qualcomm Small Cell SoC, Snapdragon Automobile, Snapdragon Mobile, and Snapdragon Wear FSM9055, IPQ4019, MDM9206, MDM9607, MDM9625, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, 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 810, SD 820, SD 820A, SD 835, SD 845, SD 850, and SDX20, when a hash is passed with zero datalength, the code returns an error, even though zero data length is valid.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This is an Android/Qualcomm platform flaw affecting many older Snapdragon-related chipsets before the Android 2018-04-05 security patch level. The described failure is a hash operation rejecting valid zero-length input. Business impact is unclear from public sources, but exposure is plausible in legacy phones, wearables, automotive, modem, and embedded Qualcomm-based devices. Organizations are most likely exposed through unmanaged or legacy Android devices, embedded systems, small-cell hardware, wearables, automotive platforms, or modems using the listed Qualcomm chipsets and patch levels before 2018-04-05. Moderate operational priority for organizations with legacy Qualcomm-based Android or embedded fleets; lower priority where patch levels are current. The main risk is unmanaged legacy exposure, not confirmed active exploitation from the provided sources. Mitigation focus: Confirm vendor firmware includes the Android 2018-04-05 security patch level or later.; Prioritize replacement for unsupported devices using listed Qualcomm chipsets.; Check OEM or carrier advisories for device-specific firmware availability..

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-10414 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.Small Cell SoC , Snapdragon Automobile, Snapdragon Mobile, Snapdragon WearFSM9055, IPQ4019, MDM9206, MDM9607, MDM9625, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, 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 810, SD 820, SD 820A, SD 835, SD 845, SD 850, SDX20Listed
Weakness

CWE details

No CWE listed

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