CVE-2017-18295
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 · uneditedPossible buffer overflow if input is not null terminated in DSP Service module in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear in version MDM9206, MDM9607, MDM9650, MSM8909W, MSM8996AU, SD 210/SD 212/SD 205, SD 450, SD 615/16/SD 415, SD 625, SD 650/52, SD 820, SD 820A, SD 835, SDX20.
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 · high confidenceA buffer overflow vulnerability exists in the DSP Service module of multiple Qualcomm Snapdragon chipsets. The issue occurs when input data is not properly null-terminated, allowing potential memory corruption. Affected components include MDM9206, MDM9607, MDM9650, MSM8909W, MSM8996AU, SD 210/212/205, SD 450, SD 615/16/415, SD 625, SD 650/52, SD 820, SD 820A, SD 835, and SDX20.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/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 chipset modelOn Android devices, run 'cat /proc/cpuinfo' or check 'Settings > About Phone' to find the chipset model. For embedded devices, check /proc/cpuinfo, or refer to device hardware documentation.Affected if The chipset matches one of: MDM9206, MDM9607, MDM9650, MSM8909W, MSM8996AU, SD 210, SD 212, SD 205, SD 450, SD 615, SD 616, SD 415, SD 625, SD 650, SD 652, SD 820, SD 820A, SD 835, SDX20
-
Verify DSP Service module is presentCheck if the DSP (Digital Signal Processor) subsystem is active on the device. On Android, this may be observable through system logs, /proc/modules, or manufacturer-provided diagnostic interfaces.Affected if The DSP Service module is loaded and running on the device
-
Confirm firmware version if accessibleIf manufacturer diagnostic tools or firmware interfaces are available, retrieve the DSP firmware version. Note that all firmware versions of the affected chipsets are vulnerable.Affected if Any DSP firmware version is present on an affected chipset (all versions are affected)
The device is affected if it contains any of the listed Qualcomm chipsets and has the DSP Service module enabled, as all firmware versions of these chipsets contain the 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-supplied firmware patches from Qualcomm through device manufacturer OTA updates. No user-level workarounds available; this requires coordinated firmware-level remediation.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18295 — 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-18295 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