dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2017-18324

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 debug messages - GERAN in snapdragon mobile and snapdragon wear in versions MDM9206, MDM9607, MDM9615, MDM9625, MDM9635M, 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 650/52, SD 800, SD 810, SD 820, SD 835, SD 855, SDX24, 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 key material is being exposed in debug messages within the GERAN (GSM/EDGE Radio Access Network) component of Qualcomm Snapdragon chipsets. This information disclosure vulnerability allows potential attackers to obtain cryptographic keys that could be used for further attacks against the cellular radio communication system.

MitigationDevice manufacturers must obtain and deploy firmware updates from Qualcomm that remove cryptographic key material from debug logging. Users should apply any available security updates from their device OEMs.

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
Mdm9625 FirmwareOperating system
Affected:all versions
Mdm9635m 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 your device's Qualcomm modem model
    Check your device specifications, about phone page, or use AT commands (AT+CGMM or AT+QCFG) to query the modem model. Compare against the list: Mdm9206, Mdm9607, Mdm9615, Mdm9625, Mdm9635m, Mdm9645, Mdm9650, Mdm9655.
    Affected if The modem model matches any of the listed affected models.
  2. Verify debug logging is enabled for the cellular modem
    Check device settings for developer options, logging settings, or diagnostic menus. On Android, examine /system/build.prop for debug properties (such as persist.radio.* or debug.* logs). Look for any setting that enables verbose GERAN or radio debug output.
    Affected if Debug logging for radio/GERAN is enabled and outputting verbose information.
  3. Inspect radio debug logs for cryptographic material
    Use logcat (adb logcat -b radio) or view device radio logs. Search for patterns indicating key material in GERAN-related log entries (any logs mentioning ciphering keys, Kc, or authentication data).
    Affected if Logs contain exposed cryptographic key material related to GERAN ciphering.
  4. Check OEM firmware version
    Query the modem firmware version via AT commands (AT+CGMR or AT+QVERS) or check the device's baseband version in settings. Compare against any available patch information from the device manufacturer.
    Affected if The firmware version is a release that has not been patched to remove key material from debug output.

You are affected if your device uses any of the listed Qualcomm modem models (Mdm9206, Mdm9607, Mdm9615, Mdm9625, Mdm9635m, Mdm9645, Mdm9650, Mdm9655) and has debug logging or diagnostic features enabled that could expose GERAN component 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

Device manufacturers must obtain and deploy firmware updates from Qualcomm that remove cryptographic key material from debug logging. Users should apply any available security updates from their device OEMs.

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation16.0 h
  • Implementation80.0 h
  • Testing24.0 h
  • Review / QA12.0 h
132.0 hours of engineering $23,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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