dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2017-18319

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
Information leak in UIM API debug messages 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, 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 · moderate confidence

This vulnerability allows an attacker to obtain sensitive information through debug messages in the UIM (User Identity Module) API. The debug logging exposes sensitive data related to SIM/USIM card operations, potentially including authentication tokens or personal identification information. The issue exists in multiple Qualcomm Snapdragon chipset firmware versions used in mobile devices and wearables.

MitigationEnterprises should inventory affected devices, apply available OEM/firmware security updates once released, and consider disabling debug interfaces in production environments. Since this is a chipset-level vulnerability, direct patching requires vendor firmware updates from device manufacturers.

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 the Qualcomm modem chipset model
    Check device specifications, modem firmware info, or AT command output (e.g., AT+CGMM, AT+CGMI) to determine if the device uses Mdm9206, Mdm9607, Mdm9615, Mdm9625, Mdm9635m, Mdm9645, Mdm9650, or Mdm9655 chipset firmware
    Affected if The device implements any of these specific Qualcomm modem chipset models in the affected list
  2. Determine the firmware version
    Query the modem firmware version via AT commands (e.g., AT+CGMR) or through device system information. Compare against the affected product list
    Affected if The firmware version corresponds to any of the listed Qualcomm Mdm products (all versions are affected)
  3. Verify debug logging status for UIM API
    Check if debug or verbose logging is enabled for the User Identity Module API. This may be configurable in modem settings, diagnostic menus, or through engineering/calibration modes accessible via AT commands or device developer options
    Affected if Debug logging for UIM operations is enabled, allowing sensitive SIM/USIM data to be written to logs
  4. Inspect UIM API logs for sensitive data exposure
    Examine modem logs, debug logs, or diagnostic output related to UIM operations (SIM/USIM card authentication, PIN operations, network registration). Look for exposure of authentication tokens, PIN codes, IMSI numbers, or other personal identification information
    Affected if Logs contain sensitive data such as authentication tokens, personal identification numbers, or PII related to SIM/USIM operations

A device is affected if it uses any of the listed Qualcomm modem chipsets (Mdm9206 through Mdm9655) and has debug logging enabled for the UIM API, resulting in sensitive SIM/USIM data appearing in logs or diagnostic 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

Enterprises should inventory affected devices, apply available OEM/firmware security updates once released, and consider disabling debug interfaces in production environments. Since this is a chipset-level vulnerability, direct patching requires vendor firmware updates from device manufacturers.

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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