Home/CVE/Wrong public key usage from existing oem_keystore for hash generation in Snapdragon Auto, Snapdragon Consumer IOT, Snapd
CVE
↯ PDF report

CVE-2019-14001

Wrong public key usage from existing oem_keystore for hash generation in Snapdragon Auto, Snapdragon Consumer IOT, Snapd

Wrong public key usage from existing oem_keystore for hash generation in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in APQ8009, APQ8017, APQ8053, APQ8096AU, MDM9206, MDM9207C, MDM9607, MDM9650, MSM8905, MSM8909W, MSM8917, MSM8953, MSM8996AU, QM215, SDM429, SDM429W, SDM439, SDM450, SDM630, SDM632, SDM636, SDM660, SDX20.

HIGH · CVSS 7.8 EPSS 0.00149
EPSS exploitation odds0.15% · top 95%
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-2019-14001, 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).
▣

Severity & exploitation scoring

View on NVD →
CVSS base score
7.8
HIGHCVSS v3.1 · [email protected]
EPSS exploitation probability
0.15%
Top 95%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.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Lifecycle
  1. 16 Apr 2020Published 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.

T1110 · Brute Force
▤ Build a SIEM detection for these techniques
▤

CAPEC attack patterns

7

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

CAPEC-CAPEC-20 · Encryption Brute Forcing CAPEC-CAPEC-459 · Creating a Rogue Certification Authority Certificate CAPEC-CAPEC-473 · Signature Spoof CAPEC-CAPEC-475 · Signature Spoofing by Improper Validation CAPEC-CAPEC-608 · Cryptanalysis of Cellular Encryption CAPEC-CAPEC-614 · Rooting SIM Cards CAPEC-CAPEC-97 · Cryptanalysis
⬡

Weakness Classification

CWE-327Use of a Broken or Risky Cryptographic Algorithm
▤

Affected Products & Versions

23
qualcomm apq8009 firmwareall versions
qualcomm apq8017 firmwareall versions
qualcomm apq8053 firmwareall versions
qualcomm apq8096au firmwareall versions
qualcomm mdm9206 firmwareall versions
qualcomm mdm9207c firmwareall versions
qualcomm mdm9607 firmwareall versions
qualcomm mdm9650 firmwareall versions
qualcomm msm8905 firmwareall versions
qualcomm msm8909w firmwareall versions
qualcomm msm8917 firmwareall versions
qualcomm msm8953 firmwareall versions
qualcomm msm8996au firmwareall versions
qualcomm qm215 firmwareall versions
qualcomm sdm429 firmwareall versions
qualcomm sdm429w firmwareall versions
qualcomm sdm439 firmwareall versions
qualcomm sdm450 firmwareall versions
qualcomm sdm630 firmwareall versions
qualcomm sdm632 firmwareall versions
qualcomm sdm636 firmwareall versions
qualcomm sdm660 firmwareall versions
qualcomm sdx20 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-0007 Information from SSL-encrypted sessions via PKCS #1. same CWE-327 CVE-2002-2058 TeeKai Tracking Online 1.0 uses weak encryption of web usage statistics in data/... same CWE-327 HIGH CVE-2005-2946 The default configuration on OpenSSL before 0.9.8 uses MD5 for creating message ... same CWE-327 HIGH CVE-2005-4860 Spectrum Cash Receipting System before 6.504 uses weak cryptography (static subs... same CWE-327 HIGH CVE-2018-13916 Out-of-bounds memory access in Qurt kernel function when using the identifier to... same product HIGH CVE-2018-11980 When a fake broadcast/multicast 11w rmf without mmie received, since no proper l... same product HIGH CVE-2019-10486 Race condition due to the lack of resource lock which will be concurrently modif... same product HIGH CVE-2019-10490 Use after free issue in Xtra daemon shutdown due to static object instance getti... same product MEDIUM
⚑

Vendor Advisories

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

References & Sources

1
Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.
https://www.qualcomm.com/company/product-security/bulletins/april-2020-bulletin
PatchVendor Advisory
◈SOC and Response
◆Detection Engineering
◎Threat Hunting
▲Red Team and Pentest
■Compliance and GRC
◯About
threatengine.sh Crafted with love in Toronto, Canada