Improper input validation for GATT data packet received in Bluetooth Controller function can lead to possible memory corruption in Snapdragon Mobile in version QCA9379, SD 210/SD 212/SD 205, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 450, SD 615/16/SD 415, SD 625, SD 650/52, SD 820, SD 835, SD 845, SD 850, SDM630, SDM636, SDM660, SDM710, Snapdragon_High_Med_2016.
CVE-2017-18171
HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2022-05-13. NVD baseline CVSS 8.8; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 8.8Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(medium)
- EPSS
- 40.2%
- KEV
- Not listed
Published
October 23, 2018
Last Modified
November 21, 2024
References (4)
- product-security@qualcommhttps://source.android.com/security/bulletin/2018-07-01#qualcomm-closed-source-components
- product-security@qualcommhttps://www.qualcomm.com/company/product-security/bulletins
- af854a3a-2127-422b-91ae-364da2661108https://source.android.com/security/bulletin/2018-07-01#qualcomm-closed-source-components
- af854a3a-2127-422b-91ae-364da2661108https://www.qualcomm.com/company/product-security/bulletins
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Frequently asked(5)
What is CVE-2017-18171?
CVE-2017-18171 is a high vulnerability published on October 23, 2018. Improper input validation for GATT data packet received in Bluetooth Controller function can lead to possible memory corruption in Snapdragon Mobile in version QCA9379, SD 210/SD 212/SD 205, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 450, SD 615/16/SD 415, SD 625, SD 650/52, SD 820, SD 835, SD…
When was CVE-2017-18171 disclosed?
CVE-2017-18171 was first published in the National Vulnerability Database on October 23, 2018, 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-18171 actively exploited?
CVE-2017-18171 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 40.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-18171?
CVE-2017-18171 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2017-18171?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-18171, 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-18171
Is Your Infrastructure Affected by CVE-2017-18171?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.