In Android for MSM, Firefox OS for MSM, QRD Android, with all Android releases from CAF using the Linux kernel, while updating the recovery message for eMMC devices, 1088 bytes of stack memory can potentially be leaked.
CVE-2017-14870
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2022-05-14. NVD baseline CVSS 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).
Internet exposure
The internet-exposure footprint is temporarily unavailable — the KEV-Exposure radar's record for this CVE could not be loaded just now. That is not a finding of zero exposed services; please retry shortly.
- CVSS v3
- 7.5
- EG Score
- 7.5HIGHmedium confidence
- EG Risk
- 38EG Risk 38/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability30% × 15%CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation. - EPSS PROB
- 0.4%
- EPSS %ILE
- 33rd
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).
A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
January 10, 2018
Last Modified
November 21, 2024
Advisory Details
Enriched advisory details are temporarily unavailable — they could not be loaded just now. That is not a sign that none exist; please retry shortly.
References (2)
- product-security@qualcommhttps://source.android.com/security/bulletin/pixel/2018-01-01
- af854a3a-2127-422b-91ae-364da2661108https://source.android.com/security/bulletin/pixel/2018-01-01
Related CVEs(same CWE)· as of October 5, 2026
Same CWE
10 shownCWE-200
Frequently asked(5)
What is CVE-2017-14870?
When was CVE-2017-14870 disclosed?
Is CVE-2017-14870 actively exploited?
What is the CVSS score of CVE-2017-14870?
How do I remediate CVE-2017-14870?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2017-14870
Is Your Infrastructure Affected by CVE-2017-14870?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.