dbcve.org
Mdm9150 FirmwareOperating system · Qualcomm

CVE-2018-13886

CRITICAL · 9.8 CVSS v3.0 Published 2019-05-24
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
Unchecked OTA field in GNSS XTRA3 lead to integer overflow and then buffer overflow in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in MDM9150, MDM9206, MDM9607, MDM9615, MDM9635M, MDM9640, MDM9650, MDM9655, MSM8909W, MSM8996AU, QCS605, Qualcomm 215, SD 210/SD 212/SD 205, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 439 / SD 429, SD 450, SD 600, SD 615/16/SD 415, SD 625, SD 632, SD 636, SD 650/52, SD 675, SD 712 / SD 710 / SD 670, SD 820, SD 820A, SD 835, SD 845 / SD 850, SDA660, SDM439, SDM630, SDM660, SDX20, SM7150, Snapdragon_High_Med_2016, 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

Unchecked OTA field in GNSS XTRA3 component allows integer overflow leading to buffer overflow, enabling potential remote code execution. This is a memory corruption vulnerability in Qualcomm baseband/GNSS firmware affecting multiple Snapdragon chipset families.

MitigationApply vendor firmware patches from Qualcomm/OEMs; until patched, reduce attack surface by disabling location services or restricting network exposure for GNSS XTRA3 functionality.

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
Mdm9150 FirmwareOperating system
Affected:all versions
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
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
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 baseband/modem chipset model
    Check the device's baseband or modem firmware information. On Android devices, go to Settings > About Phone > Baseband version, or use AT command 'AT+CGMR' via a terminal app with modem access. Look for the chipset identifier (Mdm9150, Mdm9206, Mdm9607, Mdm9615, Mdm9635m, Mdm9640, Mdm9650, or Mdm9655).
    Affected if The chipset model matches any of the affected identifiers: Mdm9150, Mdm9206, Mdm9607, Mdm9615, Mdm9635m, Mdm9640, Mdm9650, or Mdm9655.
  2. Verify the GNSS XTRA3 feature is enabled
    Check if the XTRA3 (XTRA version 3) assistance data feature is configured on the device. This may be visible in location provider settings, as a configuration file in /system/etc/gps.conf or /vendor/etc/gps.conf, or via GPS status tools that display XTRA status. Look for entries like 'XTRA3' or 'xtra3' being loaded or enabled.
    Affected if The GNSS XTRA3 feature is present and enabled on the device, as this is the vulnerable component.
  3. Confirm firmware version is unpatched
    Query the modem firmware version via AT command 'AT+CGMR' or check the baseband version shown in the device settings. Compare the version string against any vendor patch releases for CVE-2018-13886. Note that the advisory states all versions of the affected firmware are vulnerable, so any version prior to applying the specific vendor patch is affected.
    Affected if The device runs any version of the listed firmware without the CVE-2018-13886 patch applied.

If the device uses one of the affected Qualcomm modem firmware models (Mdm9150, Mdm9206, Mdm9607, Mdm9615, Mdm9635m, Mdm9640, Mdm9650, or Mdm9655) and has GNSS XTRA3 functionality enabled, the device is vulnerable to this buffer overflow vulnerability.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware patches from Qualcomm/OEMs; until patched, reduce attack surface by disabling location services or restricting network exposure for GNSS XTRA3 functionality.

Recommended fix Moderate confidence

Obtain vendor-specific patched firmware from Qualcomm or your OEM; specific fixed version numbers were not disclosed in the available reference material

  1. 1. Identify the specific chipset model(s) affected in your deployment from the list: MDM9150, MDM9206, MDM9607, MDM9615, MDM9635M, MDM9640, MDM9650, MDM9655, MSM8909W, MSM8996AU, QCS605, Qualcomm 215, SD 210/SD 212/SD 205, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 439/SD 429, SD 450, SD 600, SD 615/16/SD 415, SD 625, SD 632, SD 636, SD 650/52, SD 675, SD 712/SD 710/SD 670, SD 820, SD 820A, SD
  2. 2. Contact Qualcomm product security or your device/OEM vendor to obtain the patched firmware that addresses CVE-2018-13886
  3. 3. Request the specific security patch level (SPL) or build number containing the fix for the GNSS XTRA3 integer overflow
  4. 4. Apply the vendor-provided firmware update through the standard OEM update mechanism (OTA or manual flash)
  5. 5. Verify the patch was successfully applied by checking the firmware version or security patch level
Caveat Firmware updates may require device downtime and should be tested in a non-production environment first; verify OEM support for your specific device model

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mdm9150 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-2018-13886 — 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-2018-13886 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