dbcve.org
Mdm9607 FirmwareOperating system · Qualcomm

CVE-2017-18326

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 keys are printed in modem debug messages in snapdragon mobile and snapdragon wear in versions MDM9607, MDM9615, MDM9625, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8909W, 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 636, SD 650/52, SD 800, SD 810, SD 820, SD 835, SDA660, SDM630, 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

Cryptographic keys are being exposed in modem debug logs on affected Qualcomm Snapdragon chipsets. This is a sensitive information disclosure vulnerability where symmetric encryption keys or private keys used for cellular modem communications are being written to debug output, allowing anyone with access to the debug logs to recover the cryptographic keys and potentially decrypt communications.

MitigationApply firmware updates from the device OEM that address this vulnerability. Users should ensure their mobile devices are running the latest firmware版本 and security patches. Enterprise environments may need to audit existing device fleets for affected chipsets.

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
Mdm9615 FirmwareOperating system
Affected:all versions
Mdm9625 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 firmware model
    Use AT commands (AT+CGMM or AT+CGMI) or check the device system information to determine the modem chipset model number (e.g., Mdm9607, Mdm9615, Mdm9625, Mdm9635m, Mdm9640, Mdm9645, Mdm9650, Mdm9655)
    Affected if The modem model matches any of the affected firmware names listed in the CVE (Mdm9607, Mdm9615, Mdm9625, Mdm9635m, Mdm9640, Mdm9645, Mdm9650, Mdm9655)
  2. Verify the firmware version is unpatched
    Query the modem firmware version using AT commands (AT+CGMR) or through the device OS diagnostic interface, then confirm it is an affected version per the CVE (all versions of the listed firmware models)
    Affected if The firmware version belongs to any of the affected Mdm* models and has not been updated to a patched version
  3. Determine if modem debug logging is enabled
    Check device settings or MDM profiles for modem debug/diagnostic logging features. On Android, inspect developer options or logcat for modem log capture. On iOS, check for diagnostic reporting settings.
    Affected if Modem debug logging or diagnostic log capture is currently enabled on the device
  4. Examine debug logs for cryptographic key material
    If modem debug logs are accessible (local storage, MDM export, or logcat output), search the log contents for patterns resembling cryptographic keys: look for hexadecimal strings of 32+ bytes, PEM-style headers, or strings containing 'key', '密钥', 'encrypt', 'private' in proximity to raw key data
    Affected if Any modem debug logs contain exposed symmetric encryption keys, private keys, or key-related material in plaintext

A device is affected if it contains one of the listed Qualcomm modem firmware models (Mdm9607 through Mdm9655) with unpatched firmware and has modem debug logging enabled that exposes cryptographic keys in the output.

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 firmware updates from the device OEM that address this vulnerability. Users should ensure their mobile devices are running the latest firmware版本 and security patches. Enterprise environments may need to audit existing device fleets for affected chipsets.

Fix this in Mdm9607 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Testing16.0 h
  • Review / QA8.0 h
32.0 hours of engineering $5,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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