CVE-2017-18318
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMissing 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceMissing validation check on the CRL (Certificate Revocation List) issuer name in Snapdragon baseband/processor firmware. This flaw could allow an attacker to potentially use a malicious CRL with a spoofed issuer name to bypass certificate validation, leading to man-in-the-middle attacks or impersonation of legitimate services.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the device processor/chipset modelCheck the system-on-chip (SoC) information via /proc/cpuinfo, device settings under 'About Phone' > 'Processor', or manufacturer specifications. Look for Qualcomm Snapdragon model numbers.Affected if The chipset matches any of the following: MSM8996AU, SD 410, SD 412, SD 425, SD 430, SD 450, SD 625, or SD 650.
-
Check the baseband firmware versionOn Android devices, go to Settings > About Phone > Baseband version, or use AT command 'AT+CGMR' via a terminal app with modem diagnostics access. Record the full firmware version string.Affected if Any baseband firmware version is present on the affected chipset models, since the advisory lists 'all versions' as vulnerable.
-
Verify SSL/TLS certificate validation is in useInspect application or system network configuration to confirm SSL/TLS certificate validation is enabled. Check whether applications rely on the system's CA store and CRL checking for certificate validation.Affected if The device or its applications perform certificate validation using CRLs, and the underlying firmware does not validate CRL issuer names.
-
Confirm CRL checking is enabled in network stackReview system or application network security settings for CRL/OCSP checking configuration. On Android, this may involve checking network_security_config.xml or custom trust manager implementations.Affected if CRL-based revocation checking is actively used in the TLS/SSL validation chain on the device.
If the device uses a Qualcomm Snapdragon chipset from the affected list (MSM8996AU, SD 410, SD 412, SD 425, SD 430, SD 450, SD 625, or SD 650) and employs CRL-based certificate validation, the environment is likely affected by this vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor-provided firmware updates/patches from Qualcomm and device OEMs for the affected Snapdragon chipset versions (MSM8996AU, SD 410/12, SD 425, SD 430, SD 450, SD 625, SD 650/52, SD 810, SD 820, SD 820A).
- Consultation12.0 h
- Implementation60.0 h
- Testing32.0 h
- Review / QA16.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $33,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18318 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-18318 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data