LiveActive security incident?Get immediate response
CVE Record

CVE-2016-10434: 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 820 and SD 820A, the input to RPMB write response function is a buffer from HLOS that needs to be authenticated (using HMAC) and then processed. However, some of the processing occurs before the buffer is authenticated. The function will return various types of errors depending on the values of the `response` and `result` fields of the buffer before verifying the HMAC tag.

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

Security readout for executives and security teams

This flaw affects older Android builds on Qualcomm Snapdragon SD 820 and SD 820A platforms. A security-sensitive response buffer is partly interpreted before its integrity is checked, which can expose different error behavior. Business urgency depends on whether legacy Android, mobile, or automotive devices remain in use without the April 5, 2018 patch level. Likely limited to legacy Android devices or automotive systems using Qualcomm Snapdragon Mobile SD 820 or Snapdragon Automobile SD 820A with Android security patch levels before 2018-04-05. Exposure should be checked through asset inventory, device model, SoC, firmware, and Android security patch data. Treat this as an asset hygiene and legacy-device risk item, not an emergency based on current evidence. Prioritize confirming whether affected chipsets still exist in managed fleets, especially embedded or automotive environments where patching may lag. Mitigation focus: Confirm whether affected Snapdragon SD 820 or SD 820A assets exist.; Update affected Android devices to 2018-04-05 security patch level or later.; Check OEM, Android, and Qualcomm guidance 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-10434 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 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.