CVE-2017-18318

CRITICALNVD 9.89.8—

9.8

Missing validation check on CRL issuer name in Snapdragon Automobile, Snapdragon Mobile in versions MSM8996AU, SD 410/12, SD 425, SD 430, SD 450, SD 625, SD 650/52, SD 810, SD 820, SD 820A.

CVSS v3: 9.8
EG Score: 9.8(medium)
EPSS: 44.3%
KEV: Not listed

Published

November 28, 2018

Last Modified

November 21, 2024

References (4)

product-security@qualcommhttp://www.securityfocus.com/bid/105838
product-security@qualcommhttps://www.qualcomm.com/company/product-security/bulletins
af854a3a-2127-422b-91ae-364da2661108http://www.securityfocus.com/bid/105838
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.

CWE-20Improper Input Validation

Data Freshness Timeline

(refreshed 12× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-08 14:14 UTCepss_batch
2026-06-08 14:14 UTCepss_batch
2026-06-07 15:22 UTCepss_batch
2026-06-07 15:22 UTCepss_batch
2026-06-06 13:45 UTCepss_batch
2026-06-06 13:45 UTCepss_batch
2026-06-05 22:44 UTCepss_batch
2026-06-05 06:08 UTCepss_batch
2026-06-05 06:08 UTCepss_batch
2026-06-04 13:10 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:49 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-29 13:41 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch

Frequently asked(5)

What is CVE-2017-18318?

CVE-2017-18318 is a critical vulnerability published on November 28, 2018. Missing validation check on CRL issuer name in Snapdragon Automobile, Snapdragon Mobile in versions MSM8996AU, SD 410/12, SD 425, SD 430, SD 450, SD 625, SD 650/52, SD 810, SD 820, SD 820A.

When was CVE-2017-18318 disclosed?

CVE-2017-18318 was first published in the National Vulnerability Database on November 28, 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-18318 actively exploited?

CVE-2017-18318 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 44.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2017-18318?

CVE-2017-18318 has a CVSS v3 base score of 9.8 (NVD).

How do I remediate CVE-2017-18318?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-18318, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-18318

Explore →

Is Your Infrastructure Affected by CVE-2017-18318?

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

Start Free Scan →Browse All CVEs

CVE-2017-18318

📅 Published

🔄 Last Modified

🔗 References (4)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2017-18318?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (4)

Frequently asked(5)

Related CVEs(same CWE)