CVE-2017-18665

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.0%, top 90% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

An issue was discovered on Samsung mobile devices with M(6.0) software. There is a NULL pointer exception in WifiService via adb-cmd, causing memory corruption. The Samsung ID is SVE-2017-8287 (June 2017).

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
13.3%
KEV
Not listed

Published

April 7, 2020

Last Modified

November 21, 2024

Frequently asked(5)

What is CVE-2017-18665?
CVE-2017-18665 is a high vulnerability published on April 7, 2020. An issue was discovered on Samsung mobile devices with M(6.0) software. There is a NULL pointer exception in WifiService via adb-cmd, causing memory corruption. The Samsung ID is SVE-2017-8287 (June 2017).
When was CVE-2017-18665 disclosed?
CVE-2017-18665 was first published in the National Vulnerability Database on April 7, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-18665 actively exploited?
CVE-2017-18665 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 13.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-18665?
CVE-2017-18665 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2017-18665?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-18665, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2017-18665

Explore →

Is Your Infrastructure Affected by CVE-2017-18665?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.