dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2014-9987

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, MDM9650, SD 210/SD 212/SD 205, SD 410/12, SD 425, SD 430, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 808, SD 810, SD 820, SD 820A, SD 835, SD 845, and SD 850, a buffer over-read can occur in a DRM API.

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 over-read vulnerability exists in the DRM (Digital Rights Management) API of Qualcomm Snapdragon processors used in mobile devices, automotive systems, and wearables. The flaw allows reading beyond allocated memory boundaries, potentially exposing sensitive DRM-protected content or other memory data. Affected devices run Android versions before the 2018-04-05 security patch level across numerous Snapdragon chipset variants.

MitigationApply the April 5, 2018 or later Android security patch level to affected devices. For end-of-life devices lacking vendor patches, implement network segmentation, monitor for indicators of compromise, and consider device replacement.

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
Mdm9650 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 410 FirmwareOperating system
Affected:all versions
Sd 412 FirmwareOperating system
Affected:all versions
Sd 425 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 device chipset model
    Check the device system information or use a system info app to determine the exact Qualcomm Snapdragon model number (e.g., Mdm9206, Mdm9650, Sd 210, Sd 212, Sd 205, Sd 410, Sd 412, Sd 425)
    Affected if The chipset matches one of the affected models listed in the CVE (Mdm9206, Mdm9650, Sd 210, Sd 212, Sd 205, Sd 410, Sd 412, Sd 425)
  2. Check the Android security patch level
    Navigate to Settings > About Phone > Security Patch Level on the Android device to view the installed patch date
    Affected if The security patch level is earlier than April 5, 2018 (2018-04-05)
  3. Verify the device runs Android
    Confirm the device operating system is Android by checking Settings > About Phone > Android version
    Affected if The device runs Android (the vulnerability affects Android devices with these chipsets)
  4. Confirm DRM API usage
    Review installed applications that utilize DRM-protected content (video streaming apps, media players, content providers) or check if Widevine or other DRM frameworks are active on the device
    Affected if DRM-protected content services or DRM APIs are actively used on the device, exposing the vulnerable interface

The device is affected if it uses one of the listed Qualcomm Snapdragon chipsets and has a security patch level earlier than April 5, 2018, especially if DRM services are actively used.

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 the April 5, 2018 or later Android security patch level to affected devices. For end-of-life devices lacking vendor patches, implement network segmentation, monitor for indicators of compromise, and consider device replacement.

Recommended fix High confidence

Android Security Patch Level 2018-04-05 or later (for affected Snapdragon variants: MDM9206, MDM9650, SD 210, SD 212, SD 205, SD 410, SD 412, SD 425)

  1. Verify the current Android security patch level on the device by going to Settings > About Phone > Security Patch Level
  2. Update the device to Android security patch level 2018-04-05 or later
  3. For devices that no longer receive official security updates from the OEM, consider replacing with a device that receives regular security updates
  4. If the device is an embedded IoT/device product, contact the device manufacturer for a firmware update that includes the April 2018 security patch

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
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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