dbcve.org
Sd 210 FirmwareOperating system · Qualcomm

CVE-2015-9205

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 MSM8909W, SD 210/SD 212/SD 205, SD 410/12, SD 615/16/SD 415, SD 808, and SD 810, in a PlayReady API function, a buffer over-read can occur.

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 PlayReady API function on multiple older Qualcomm Snapdragon mobile and wearable chipsets (MSM8909W, SD 210/212/205, SD 410/12, SD 615/16/415, SD 808, SD 810). The flaw allows reading beyond allocated buffer boundaries, potentially enabling memory disclosure or remote code execution given the critical CVSS 9.8 score.

MitigationApply the April 2018 or later Android security patch level to affected devices, or replace devices that cannot receive vendor firmware updates.

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
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 615 FirmwareOperating system
Affected:all versions
Sd 616 FirmwareOperating system
Affected:all versions
Sd 415 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 your device chipset model
    Check device settings under 'About Phone' > 'Hardware' or use ADB command: 'getprop ro.board.platform' or 'cat /proc/cpuinfo'
    Affected if The chipset matches one of these: SD 210, SD 212, SD 205, SD 410, SD 412, SD 615, SD 616, SD 415, or MSM8909W, SD 808, SD 810
  2. Confirm PlayReady DRM is enabled
    Check device DRM settings: Settings > Security > DRM info, or Settings > Apps > All > Google Play Services > Permissions to verify PlayReady is active
    Affected if PlayReady DRM is present and enabled on the device
  3. Check Android security patch level
    Use Settings > About Phone > Android security patch level, or run: 'getprop ro.build.version.security_patch'
    Affected if Security patch level is earlier than April 2018 (any date before 2018-04-01)
  4. Verify baseband firmware version
    Run: 'getprop | grep baseband' via ADB or check Settings > About Phone > Baseband version
    Affected if Baseband version corresponds to firmware released before the April 2018 Qualcomm update

Your device is affected if it uses any of the listed Snapdragon chipsets (SD 210/212/205/410/412/615/616/415/808/810) and has an Android security patch level earlier than April 2018 with PlayReady DRM enabled.

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 2018 or later Android security patch level to affected devices, or replace devices that cannot receive vendor firmware updates.

Recommended fix High confidence

Android Security Patch Level April 2018 or later (provided by OEM)

  1. 1. Apply Android security patch level 2018-04-05 or later to the affected device
  2. 2. Contact the device OEM (Original Equipment Manufacturer) to ensure the April 2018 Qualcomm security patch has been applied
  3. 3. Verify the device is running Android security patch level April 2018 or later via Settings > About Phone > Android security patch level
  4. 4. If the OEM no longer provides updates, consider migrating to a device that receives regular security patches
Caveat Older devices may no longer receive OEM security updates; end-of-life devices may require replacement

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

Fix this in Sd 210 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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