dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2018-13888

HIGH · 7.8 CVSS v3.0 Published 2019-02-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
There is potential for memory corruption in the RIL daemon due to de reference of memory outside the allocated array length in RIL in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables in versions MDM9206, MDM9607, MDM9635M, MDM9650, MSM8909W, SD 210/SD 212/SD 205, SD 425, SD 427, SD 430, SD 435, SD 439 / SD 429, SD 450, SD 625, SD 636, SD 650/52, SD 675, SD 712 / SD 710 / SD 670, SD 820A, SD 835, SD 845 / SD 850, SD 855, SDM439, SDM630, SDM660, ZZ_QCS605.

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

Memory corruption vulnerability in the RIL (Radio Interface Layer) daemon where memory is dereferenced outside the allocated array bounds. This out-of-bounds access in the RIL component can lead to memory corruption potentially allowing code execution or denial of service.

MitigationApply vendor-provided firmware/security updates from Qualcomm and device manufacturers. Users should check for and install available patches through their device OEM's security update channel.

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
Mdm9635m FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions
Msm8909w FirmwareOperating system
Affected:all versions
Sd 210 FirmwareOperating system
Affected:all versions
Sd 212 FirmwareOperating system
Affected:all versions
Sd 205 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
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/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 Qualcomm modem chip model
    Check the baseband or modem firmware version via AT command 'AT+CGMR' or through the device's about phone/settings menu. On Linux systems, check /proc/cpuinfo or /sys/class/net/*/device for modem identifiers.
    Affected if The device uses one of these Qualcomm modem models: Mdm9206, Mdm9607, Mdm9635m, Mdm9650, Msm8909w, Sd 210, Sd 212, or Sd 205.
  2. Verify the RIL daemon is present
    Check if the RIL (Radio Interface Layer) daemon is running on the device. On Android, look for rild or reference-rild processes via 'ps | grep rild' or check /system/bin for rild binaries.
    Affected if The device runs a RIL daemon (rild) for cellular radio communication.
  3. Confirm baseband firmware version
    Retrieve the baseband version string from the device. On Android: Settings > About Phone > Baseband version, or via 'getprop gsm.version.baseband' command. On Linux: check /proc/ version or use AT commands.
    Affected if The baseband version matches one of the affected firmware variants listed (all versions of Mdm9206, Mdm9607, Mdm9635m, Mdm9650, Msm8909w, Sd 210, Sd 212, Sd 205).

The device is affected if it contains any of the listed Qualcomm modem chips (Mdm9206, Mdm9607, Mdm9635m, Mdm9650, Msm8909w, Sd 210, Sd 212, Sd 205) and runs a RIL daemon, since all firmware versions of these chips are vulnerable to the out-of-bounds memory access.

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-provided firmware/security updates from Qualcomm and device manufacturers. Users should check for and install available patches through their device OEM's security update channel.

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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