dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2014-9990

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 Mobile and Snapdragon Wear MDM9206, MDM9607, MDM9615, MDM9625, MDM9635M, MSM8909W, SD 210/SD 212/SD 205, SD 410/12, SD 425, SD 430, SD 600, SD 615/16/SD 415, SD 625, SD 650/52, SD 808, SD 810, and SD 450, lack of input validation could lead to an out of bound array access.

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

A firmware-level vulnerability in Qualcomm Snapdragon chipsets where insufficient input validation allows out-of-bounds array access, potentially enabling code execution or denial of service. This affects multiple Snapdragon Mobile and Wear platform variants.

MitigationApply Android security patch level 2018-04-05 or later to affected devices; for enterprise deployments, identify and inventory vulnerable Snapdragon-based devices and ensure vendor firmware updates are applied.

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
Msm8909w FirmwareOperating system
Affected:all versions
Sd 210 FirmwareOperating system
Affected:all versions
Sd 212 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 Qualcomm chipset model
    Check the device's processor/chipset information through /proc/cpuinfo, system settings about phone, or device manufacturer documentation. For modem-specific info, use AT command AT+CGMM via serial terminal to the modem subsystem.
    Affected if The chipset matches one of these models: Mdm9206, Mdm9607, Mdm9615, Mdm9625, Mdm9635m, Msm8909w, Sd 210, or Sd 212
  2. Retrieve the baseband or modem firmware version
    Use AT command AT+CGMR (or AT+VERSION depending on carrier) to query the modem firmware version. On Android, also check through Settings > About Phone > Baseband version, or via adb shell with getprop ro.baseband or getprop gsm.version.baseband.
    Affected if The firmware version cannot be determined or shows a version predating the 2018-04-05 security patch level
  3. Check the Android security patch level
    On Android, go to Settings > About Phone > Android security patch level, or run: adb shell getprop ro.build.version.security_patch
    Affected if The security patch level is earlier than 2018-04-05 or the field is empty/unavailable
  4. Verify if the device receives vendor firmware updates
    Contact the device manufacturer or mobile carrier (if branded) to confirm whether firmware updates addressing this CVE are available for your specific model and region.
    Affected if The manufacturer confirms no update is available for your device model or the update schedule is unknown

The device is affected if it uses any of the listed Snapdragon chipset models (Mdm9206, Mdm9607, Mdm9615, Mdm9625, Mdm9635m, Msm8909w, Sd 210, Sd 212) and the installed firmware predates the 2018-04-05 patch level or cannot be verified.

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 to affected devices; for enterprise deployments, identify and inventory vulnerable Snapdragon-based devices and ensure vendor firmware updates are applied.

Recommended fix Moderate confidence

Android Security Patch Level 2018-04-05 or later (contact OEM for specific firmware version)

  1. Contact the device OEM (Original Equipment Manufacturer) for the specific firmware update containing the Android security patch level from 2018-04-05 or later
  2. Apply the OEM-provided security update to address the out-of-bounds array access vulnerability
  3. Verify the installed security patch level is 2018-04-05 or later via Settings > About Phone > Security Patch Level
Caveat OEM-specific update; verify device compatibility before applying

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
  • Testing16.0 h
  • Review / QA8.0 h
32.0 hours of engineering $5,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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