dbcve.org
Mdm9607 FirmwareOperating system · Qualcomm

CVE-2017-18311

HIGH · 7.8 CVSS v3.0 Published 2018-10-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
XPU Master privilege escalation is possible due to improper access control of unused configuration xPU ports where unused configuration ports are open in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear in version MDM9607, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8909W, MSM8996AU, 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 810, SD 820, SD 820A, SD 835, SDA660, SDM429, SDM439, SDM630, SDM632, SDM636, SDM660, Snapdragon_High_Med_2016.

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

Improper access control on unused configuration xPU ports in Qualcomm Snapdragon processors allows privilege escalation to XPU Master level. Attackers with lower privilege access could potentially exploit these open unused configuration ports to gain elevated privileges.

MitigationRequires Qualcomm firmware patch distributed via OEM OTA updates. No end-user mitigation available; users must await vendor patches.

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
Mdm9607 FirmwareOperating system
Affected:all versions
Mdm9635m FirmwareOperating system
Affected:all versions
Mdm9640 FirmwareOperating system
Affected:all versions
Mdm9645 FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions
Mdm9655 FirmwareOperating system
Affected:all versions
Msm8909w FirmwareOperating system
Affected:all versions
Msm8996au 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
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 checks

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

  1. Identify the Qualcomm chipset model
    Check your device specifications or use a system info tool to determine if the device uses one of the affected Qualcomm processors: Mdm9607, Mdm9635m, Mdm9640, Mdm9645, Mdm9650, Mdm9655, Msm8909w, or Msm8996au
    Affected if The device contains any of these specific Qualcomm chipset models
  2. Check the installed firmware version
    Access the device's firmware/build information through the bootloader, about phone settings, or by querying the baseband version via AT commands or system diagnostics
    Affected if Firmware version cannot be verified as patched, since all versions of the listed chipsets are affected
  3. Verify xPU port accessibility
    Analyze the firmware configuration or memory map to determine if unused XPU configuration ports are exposed and accessible to lower-privilege software contexts
    Affected if Unused xPU configuration ports are present and accessible without proper access controls
  4. Confirm privilege context of current attacker
    Review system logs or security audits to determine if any untrusted or lower-privilege code or processes exist on the device that could potentially access the xPU ports
    Affected if The device runs any untrusted applications or allows third-party code execution at lower privilege levels

You are affected if your device uses any of the listed Qualcomm Snapdragon chipsets (Mdm9607, Mdm9635m, Mdm9640, Mdm9645, Mdm9650, Mdm9655, Msm8909w, Msm8996au) and runs firmware that has not been patched by the OEM, since all versions of these chipsets contain the improper access control on unused xPU configuration ports.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Requires Qualcomm firmware patch distributed via OEM OTA updates. No end-user mitigation available; users must await vendor patches.

Fix this in Mdm9607 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation40.0 h
  • Testing24.0 h
  • Review / QA8.0 h
80.0 hours of engineering $13,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-18311 — 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-18311 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