dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2014-9993

CRITICAL · 9.8 CVSS v3.0 Published 2018-04-18
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
In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile, Snapdragon Mobile, and Snapdragon Wear MDM9206, MDM9607, MDM9650, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 430, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 810, SD 820, SD 820A, SD 835, SD 845, SD 450, and SD 850, buffer overread vulnerability may occur while provisioning a content with a large message.

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

A buffer overread vulnerability exists in the content provisioning functionality of Qualcomm Snapdragon chipsets. When provisioning content with a message exceeding expected size boundaries, the system reads beyond the allocated buffer, potentially exposing sensitive memory contents or enabling remote code execution. This affects multiple Snapdragon platform variants including mobile, automotive, and wearable chipsets.

MitigationApply Android security patch level 2018-04-05 or later, which contains the fix for this vulnerability in the affected Snapdragon chipset drivers. Contact device OEMs for firmware updates if not receiving OTA patches.

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
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
Sd 400 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 chipset model
    Check the device specifications or system information to determine the Qualcomm Snapdragon chipset model. This may be found in /proc/cpuinfo, device settings under 'About Phone', or OEM documentation.
    Affected if The chipset model matches one of the following: Mdm9206, Mdm9607, Mdm9650, Msm8909w, Sd 210, Sd 212, Sd 205, or Sd 400.
  2. Check firmware version
    Retrieve the firmware version for the identified chipset. On affected devices, this is typically available through carrier engineering menus, device diagnostics, or by querying the baseband version via AT commands or system logs.
    Affected if Any firmware version is returned for an affected chipset model, since all versions are listed as vulnerable.
  3. Determine if content provisioning is in use
    Check if the device or network configuration involves content provisioning functionality. This feature is typically used by mobile carriers for remote SIM provisioning, OTA updates, or device management. Inspect relevant logs or configuration files for provisioning-related processes.
    Affected if Content provisioning features are enabled or actively used on the device.
  4. Verify Android security patch level
    Check the Android security patch level by going to Settings > About Phone > Software Information, or by running 'getprop ro.build.version.security_patch' via ADB.
    Affected if The security patch level is earlier than 2018-04-05, indicating the fix has not been applied.

The environment is affected if the device uses one of the listed Qualcomm chipset models (Mdm9206, Mdm9607, Mdm9650, Msm8909w, Sd 210, Sd 212, Sd 205, or Sd 400) and the Android security patch level is earlier than 2018-04-05, especially if content provisioning functionality is in use.

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 Android security patch level 2018-04-05 or later, which contains the fix for this vulnerability in the affected Snapdragon chipset drivers. Contact device OEMs for firmware updates if not receiving OTA patches.

Recommended fix High confidence

Android security patch level 2018-04-05 or later (contact OEM for specific update)

  1. 1. Identify all affected devices in your inventory that use the listed Qualcomm Snapdragon firmware versions (MDM9206, MDM9607, MDM9650, MSM8909W, SD 210, SD 212, SD 205, SD 400)
  2. 2. Check the current Android security patch level on each affected device
  3. 3. If the device's security patch level is earlier than 2018-04-05, the device is vulnerable
  4. 4. Contact the device manufacturer (OEM) to obtain a firmware update with the April 2018 or later security patch level
  5. 5. Apply the manufacturer-provided security update to remediate the buffer overread vulnerability
  6. 6. If no update is available from the OEM, consider replacing the affected device with a newer model that receives regular security updates
  7. 7. As a temporary mitigation, restrict network access to vulnerable devices and avoid provisioning them with untrusted content
Caveat Older embedded devices may reach end-of-life and no longer receive security updates from OEMs

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

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing16.0 h
  • Review / QA8.0 h
36.0 hours of engineering $6,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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