dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2017-18314

CRITICAL · 9.8 CVSS v3.0 Published 2018-09-20
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 Snapdragon (Automobile, Mobile, Wear) in version MDM9206, 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 617, SD 625, SD 650/52, SD 810, SD 820, SD 820A, SD 835, SDA660, SDM429, SDM439, SDM630, SDM632, SDM636, SDM660, Snapdragon_High_Med_2016, on TZ cold boot the CNOC_QDSS RG0 locked by xBL_SEC is cleared by TZ.

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

During TrustZone cold boot, the CNOC_QDSS RG0 security register—previously locked by the early bootloader (xBL_SEC)—is incorrectly cleared by TZ itself. This allows a bypass of security boundaries in the trusted execution environment, potentially enabling privilege escalation or secure boot circumference.

MitigationApply vendor firmware patches from Qualcomm and affected device OEMs; verify all deployed devices run patched firmware versions to remediate the TrustZone security bypass.

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
Mdm9206 FirmwareOperating system
Affected:all versions
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

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. Identify the Qualcomm chipset/firmware model
    Retrieve the modem or chipset identifier from the device (e.g., via AT commands like AT+CGMM, diag interface, or system logs showing the baseband processor info)
    Affected if The chipset model matches Mdm9206, Mdm9607, Mdm9635m, Mdm9640, Mdm9645, Mdm9650, Mdm9655, or Msm8909w (all versions of these are affected)
  2. Check the baseband firmware version
    Query the baseband firmware version through diag ports, AT commands (AT+CGMR), or manufacturer diagnostic tools provided by the OEM
    Affected if The firmware version corresponds to any version of the affected Qualcomm products listed above (all versions are vulnerable)
  3. Verify TrustZone configuration access
    If you have access to the TrustZone debug interface or secure boot logs, inspect whether the CNOC_QDSS RG0 register state is retained or cleared during cold boot (this requires low-level hardware or diag access)
    Affected if The CNOC_QDSS RG0 security register is found to be cleared when it should remain locked by xBL_SEC (indicating the vulnerability is present)
  4. Check for vendor patch status
    Contact the device OEM or check release notes for the baseband firmware to determine if a security patch addressing CVE-2017-18314 has been applied
    Affected if No specific patch for CVE-2017-18314 is listed in the firmware release notes and the device uses an affected chipset

A device is affected if it contains any of the listed Qualcomm chipsets (Mdm9206, Mdm9607, Mdm9635m, Mdm9640, Mdm9645, Mdm9650, Mdm9655, Msm8909w) and the firmware has not been patched to address this TrustZone bypass, as all firmware versions of these products are vulnerable.

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

Apply vendor firmware patches from Qualcomm and affected device OEMs; verify all deployed devices run patched firmware versions to remediate the TrustZone security bypass.

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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