dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2015-9210

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, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 430, SD 450, 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, and SD 850, lack of input validation in playready_licacq_process_response() can lead to memory over read.

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

This vulnerability exists in the PlayReady DRM (Digital Rights Management) component within Qualcomm Snapdragon chipset firmware. Specifically, the playready_licacq_process_response() function lacks proper input validation when processing license acquisition responses, allowing an attacker to trigger a memory over-read condition. This could enable arbitrary memory disclosure, potentially leading to information leakage or协助 further exploitation.

MitigationApply the Android security patch level from 2018-04-05 or later, which contains the vendor-supplied firmware fix from Qualcomm. Users should ensure their device manufacturers have released and installed the appropriate security update for their specific Snapdragon chipset.

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
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
Sd 410 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 Snapdragon chipset model
    Check the device specifications or use system information tools (such as 'getprop' on Android, checking /proc/cpuinfo, or reviewing the device's technical documentation) to determine the exact Snapdragon chipset model number
    Affected if The chipset model is one of: Mdm9206, Mdm9650, Msm8909w, Sd 210, Sd 212, Sd 205, Sd 400, or Sd 410
  2. Verify the firmware version of the Snapdragon component
    Use manufacturer-provided tools or AT commands (such as 'AT+VER' or 'AT+QCFG') to query the firmware version of the baseband or modem processor where the PlayReady DRM component resides
    Affected if The firmware version matches any version of the affected chipset models listed above (all versions are affected)
  3. Confirm PlayReady DRM is in use
    Check if the device application or media framework invokes PlayReady DRM functionality. This may be observable through DRM license logs, debug traces, or by inspecting which DRM engines are registered in the system (check /system/etc/firmware or DRM configuration files)
    Affected if PlayReady DRM is enabled and actively processing license acquisition responses on the device
  4. Check the Android security patch level
    On the Android device, go to Settings > About Phone > Build Number, or use 'getprop ro.build.version.security_patch' command to retrieve the installed security patch level
    Affected if The security patch level is earlier than 2018-04-05, indicating the vendor-supplied firmware fix has not been applied

The device is affected if it uses any of the affected Qualcomm Snapdragon chipset models (Mdm9206, Mdm9650, Msm8909w, Sd 210, Sd 212, Sd 205, Sd 400, or Sd 410) and the Android security patch level is earlier than 2018-04-05.

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 Android security patch level from 2018-04-05 or later, which contains the vendor-supplied firmware fix from Qualcomm. Users should ensure their device manufacturers have released and installed the appropriate security update for their specific Snapdragon chipset.

Recommended fix Moderate confidence

Android security patch level April 5, 2018 or later (or May 2018 / June 2018 security patch which includes the fix)

  1. Check current Android security patch level on affected device (Settings > About Phone > Security patch level)
  2. If the security patch level is earlier than April 5, 2018, apply the latest available Android security update from your device manufacturer
  3. Verify that after update, the security patch level shows April 2018 or later

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

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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