dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2017-18323

MEDIUM · 5.5 CVSS v3.0 Published 2019-01-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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
Cryptographic key material leaked in TDSCDMA RRC debug messages in snapdragon automobile, snapdragon mobile and snapdragon wear in versions MDM9206, MDM9607, MDM9615, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8909W, MSM8996AU, SD 210/SD 212/SD 205, SD 410/12, SD 425, SD 430, SD 450, SD 615/16/SD 415, SD 625, SD 650/52, SD 712 / SD 710 / SD 670, SD 820, SD 820A, SD 835, SD 845 / SD 850, SDA660, SDX20, SXR1130.

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

Cryptographic key material is being exposed in TD-SCDMA RRC (Radio Resource Control) debug messages on affected Snapdragon chipsets. An attacker with access to debug outputs could potentially recover encryption keys used for securing wireless communications, compromising the confidentiality of encrypted traffic.

MitigationApply vendor firmware updates from Qualcomm that remove or properly secure debug message logging. Users should apply security patches from device manufacturers once OEM updates become available.

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
Mdm9615 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

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
None
Availability
None

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 modem chipset model
    Check the device specifications or use AT commands (e.g., AT+CGMM or AT+QCFG) to query the modem model. On Linux, check /proc/cpuinfo or lsusb for Qualcomm modem identifiers.
    Affected if The modem model is one of: Mdm9206, Mdm9607, Mdm9615, Mdm9635m, Mdm9640, Mdm9645, Mdm9650, or Mdm9655.
  2. Confirm TD-SCDMA network support is enabled
    Check modem configuration for TD-SCDMA (Band 34/39) support. Use AT commands such as AT+QCFG="nbrctrl" or inspect the modem's network band configuration. On Android, check via *#*#4636#*#* or cellular carrier settings.
    Affected if TD-SCDMA bands are enabled or the device is configured to connect to TD-SCDMA networks.
  3. Verify debug logging is enabled for RRC messages
    Inspect modem debug settings. Check for verbose RRC (Radio Resource Control) logging flags in /etc/ or /vendor/ configuration files, or via AT+QDEBUG commands if available. Look for settings that enable RRC message dumping.
    Affected if Debug logging for RRC messages is turned on in the modem firmware configuration.
  4. Inspect debug outputs for cryptographic key material
    Capture and review modem debug logs or baseband dumps. Search for patterns indicating exposed key material in TD-SCDMA RRC messages, such as ciphering keys (Kc, CK, IK) or security algorithm parameters in plaintext debug strings.
    Affected if Debug output contains visible encryption keys or key material related to TD-SCDMA RRC procedures.

The device is affected if it uses one of the listed Qualcomm modem chipsets, has TD-SCDMA support enabled, and has debug logging active that exposes RRC messages containing cryptographic key material.

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 updates from Qualcomm that remove or properly secure debug message logging. Users should apply security patches from device manufacturers once OEM updates become available.

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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