Home/CVE/In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile and Snapdragon Mobile SD
CVE
↯ PDF report

CVE-2016-10428

In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile and Snapdragon Mobile SD

In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile and Snapdragon Mobile SD 425, SD 430, SD 450, SD 625, SD 650/52, SD 820, and SD 820A, HMAC verification in counter file uses an insecure memcmp which may assist a timing attack.

HIGH · CVSS 7.5 EPSS 0.00887
EPSS exploitation odds0.89% · top 44%
Schedule remediation
  • CVSS base score ≥ 7.0
No Sigma yet — build one → YARA rules0
Look this up elsewhere - one-click external pivots
NVDCVE.orgCISAExploit-DBGitHub PoCVulnCheck KEVGreyNoise
▸ How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2016-10428, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked. EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal. CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score. Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits. PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
↗

Exploitation momentum

41 days of EPSS
dormant
Flat and low - no real exploitation pressure. This reads the direction and speed of EPSS over time, which can move before EPSS itself peaks or before CISA lists it.
Window
▣

Severity & exploitation scoring

View on NVD →
CVSS base score
7.5
HIGHCVSS v3.0 · [email protected]
EPSS exploitation probability
0.89%
Top 44%odds of exploitation in the next 30 days
CVSS metric silhouette
VectorComplexityPrivilegesInteractionScopeConfidentialityIntegrityAvailability
shape grows toward worst-case
SSVC triage
No SSVC vulnrichment for this CVE. CISA's Vulnrichment program scores newer CVEs (~2024 onwards) plus selected older critical ones. Use the EPSS probability + KEV status to triage instead.
CVSS vector breakdown
Exploitability - how they get in
Attack Vector
Network Adjacent Local Physical
Attack Complexity
Low High
Privileges Required
None Low High
User Interaction
None Required
Scope
Unchanged Changed
Impact - what breaks
Confidentiality
None Low High
Integrity
None Low High
Availability
None Low High
VECTORCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Lifecycle
  1. 18 Apr 2018Published to NVD
  2. 17 Jun 2026Last modified
Every entry is a recorded date - NVD publish/modify, CISA KEV add, public exploit disclosure. No inferred events.
Attack path
Full kill chain
→
◆

ATT&CK techniques

1

Techniques this CVE enables. Pills with a solid outline are high confidence - named directly in ATT&CK or Nuclei, or human-curated by CTID; the rest are inferred from the weakness type using MITRE's CVE Mapping Methodology and the CWE → CAPEC chain. Broad, generic-weakness guesses are filtered out. A small N× marks a technique that N independent sources agree on.

T1190 · Exploit Public-Facing Application
▤ Build a SIEM detection for these techniques
▤

CAPEC attack patterns

12

Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.

CAPEC-CAPEC-116 · Excavation CAPEC-CAPEC-13 · Subverting Environment Variable Values CAPEC-CAPEC-169 · Footprinting CAPEC-CAPEC-22 · Exploiting Trust in Client CAPEC-CAPEC-224 · Fingerprinting CAPEC-CAPEC-285 · ICMP Echo Request Ping CAPEC-CAPEC-287 · TCP SYN Scan CAPEC-CAPEC-290 · Enumerate Mail Exchange (MX) Records CAPEC-CAPEC-291 · DNS Zone Transfers CAPEC-CAPEC-292 · Host Discovery CAPEC-CAPEC-293 · Traceroute Route Enumeration CAPEC-CAPEC-294 · ICMP Address Mask Request
⬡

Weakness Classification

CWE-200Exposure of Sensitive Information to an Unauthorized Actor
▤

Affected Products & Versions

8
qualcomm sd 425 firmwareall versions
qualcomm sd 430 firmwareall versions
qualcomm sd 450 firmwareall versions
qualcomm sd 625 firmwareall versions
qualcomm sd 650 firmwareall versions
qualcomm sd 652 firmwareall versions
qualcomm sd 820 firmwareall versions
qualcomm sd 820a firmwareall versions
▤

Related CVEs

8
CVEs linked to this one by a shared weakness (CWE) or affected product - joins on data already in the engine, with the reason shown per row.
CVE-1999-0059 IRIX fam service allows an attacker to obtain a list of all files on the server. same CWE-200 HIGH CVE-1999-0524 ICMP information such as (1) netmask and (2) timestamp is allowed from arbitrary... same CWE-200 MEDIUM CVE-1999-1136 Vulnerability in Predictive on HP-UX 11.0 and earlier, and MPE/iX 5.5 and earlie... same CWE-200 CVE-1999-0453 An attacker can identify a CISCO device by sending a SYN packet to port 1999, wh... same CWE-200 CVE-2014-10048 In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdra... same product CRITICAL CVE-2014-10053 In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdra... same product CRITICAL CVE-2014-10054 In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdra... same product CRITICAL CVE-2014-10057 In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdra... same product CRITICAL
⚑

Vendor Advisories

1
android-securityANDROID-2018-04-01High
🔗

References & Sources

2
Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.
http://www.securityfocus.com/bid/103671
Third Party AdvisoryVDB Entry
https://source.android.com/security/bulletin/2018-04-01
Vendor Advisory
◈SOC and Response
◆Detection Engineering
◎Threat Hunting
▲Red Team and Pentest
■Compliance and GRC
◯About
threatengine.sh Crafted with love in Toronto, Canada