dbcve.org
Mdm9650 FirmwareOperating system · Qualcomm

CVE-2017-18135

CRITICAL · 9.8 CVSS v3.0 Published 2018-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
In Android before security patch level 2018-04-05 on Qualcomm Snapdragon Mobile MDM9650, MDM9655, SD 450, SD 625, SD 650/52, SD 835, SD 845, SD 850, in the Wireless Data Service (WDS) module, a buffer overflow can occur.

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 confidence

Buffer overflow vulnerability in the Wireless Data Service (WDS) module of Qualcomm Snapdragon mobile processors (MDM9650, MDM9655, SD 450, SD 625, SD 650/52, SD 835, SD 845, SD 850) on Android devices before the 2018-04-05 security patch level, potentially allowing remote code execution or denial of service.

MitigationApply Android security patch level 2018-04-05 or later to affected devices; device manufacturers must push firmware updates to close this vulnerability.

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 data
Mdm9650 FirmwareOperating system
Affected:all versions
Mdm9655 FirmwareOperating system
Affected:all versions
Sd 450 FirmwareOperating system
Affected:all versions
Sd 625 FirmwareOperating system
Affected:all versions
Sd 650 FirmwareOperating system
Affected:all versions
Sd 652 FirmwareOperating system
Affected:all versions
Sd 835 FirmwareOperating system
Affected:all versions
Sd 845 FirmwareOperating system
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Android security patch level
    Open Settings > About Phone > Android security patch level, or run 'adb shell getprop ro.build.version.security_patch'
    Affected if The patch level is earlier than 2018-04-05 (e.g., 2018-03-05, 2018-02-05, or older)
  2. Identify the Snapdragon chipset model
    Open Settings > About Phone > Model, or run 'adb shell getprop ro.product.board' or 'adb shell getprop ro.mediatek.platform' to identify the SoC; cross-reference with the device's full specifications
    Affected if The chipset is one of: MDM9650, MDM9655, SD 450, SD 625, SD 650, SD 652, SD 835, or SD 845
  3. Verify WDS module availability
    Run 'adb shell service list | grep wds' or check if the Wireless Data Service interface is accessible via 'adb shell dumpsys'
    Affected if The WDS (Wireless Data Service) module is present and exposed on the device

A device is affected if it runs an Android security patch level before 2018-04-05 AND uses one of the listed Qualcomm Snapdragon chipsets with the WDS module enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Android security patch level 2018-04-05 or later to affected devices; device manufacturers must push firmware updates to close this vulnerability.

Recommended fix High confidence

Android Security Patch Level 2018-04-05 or later (contact device manufacturer for specific update)

  1. 1. Identify the device model and confirm it uses an affected Qualcomm Snapdragon chipset (MDM9650, MDM9655, SD 450, SD 625, SD 650/52, SD 835, SD 845, or SD 850)
  2. 2. Verify the current Android security patch level on the device (Settings > About Phone > Security Patch Level)
  3. 3. Apply the Android security update for April 2018 or later (2018-04-05 patch level or higher)
  4. 4. If the device manufacturer has released a firmware update addressing this vulnerability, apply that firmware update
  5. 5. Verify the security patch level has been successfully updated after applying the patch
Caveat Device must receive manufacturer support; older devices may no longer receive security updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mdm9650 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,360
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-18135 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-18135 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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