dbcve.org
Msm8909w FirmwareOperating system · Qualcomm

CVE-2015-9130

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 400, SD 410/12, SD 615/16/SD 415, SD 617, SD 650/52, SD 808, and SD 810, in a PlayReady function, a NULL pointer dereference 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 NULL pointer dereference vulnerability exists in the PlayReady DRM function within Qualcomm Snapdragon processors (MSM8909W, SD 210/212/205, SD 400, SD 410/12, SD 615/16/415, SD 617, SD 650/52, SD 808, SD 810) on Android devices with security patch levels before April 2018. This memory handling flaw in the firmware could allow remote code execution or denial of service.

MitigationApply the April 2018 Android security patch or later, which includes the Qualcomm firmware fix; devices no longer receiving security updates should be replaced.

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
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
Sd 412 FirmwareOperating system
Affected:all versions
Sd 615 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 processor model
    Check the device specifications or use a system info app to determine the exact Snapdragon processor model (such as MSM8909W, SD 210, SD 212, SD 205, SD 400, SD 410, SD 412, SD 615, SD 616, SD 415, SD 617, SD 650, SD 652, SD 808, or SD 810).
    Affected if The processor matches one of the affected models listed in the CVE (MSM8909W, SD 210/212/205, SD 400, SD 410/12, SD 615/16/415, SD 617, SD 650/52, SD 808, or SD 810).
  2. Check the Android security patch level
    Go to Settings > About Phone > Security patch level on the Android device to view the installed security update date.
    Affected if The security patch level is dated before April 2018 (for example, March 2018 or earlier).
  3. Confirm PlayReady DRM usage
    PlayReady is a DRM technology typically embedded in media applications and the firmware itself; this is implicitly present on most Android devices that support protected media content.
    Affected if The device processes protected media content that utilizes PlayReady DRM (this is typically enabled by default on affected devices).

The device is affected if it uses one of the listed Qualcomm Snapdragon processors and has an Android security patch level dated before April 2018.

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 Android security patch or later, which includes the Qualcomm firmware fix; devices no longer receiving security updates should be replaced.

Recommended fix High confidence

Android Security Patch Level 2018-04-05 or later (contact device OEM for specific build numbers)

  1. Verify the current Android security patch level on the device by going to Settings > About Phone > Build Number or Settings > Security > Security Patch Level
  2. Update the device to Android security patch level 2018-04-05 or later. This can be done via: Settings > System > System Updates (or Software Update) on supported devices
  3. If the device manufacturer has not released an update, contact the device manufacturer (OEM) for the appropriate firmware patch that includes the April 2018 Android security bulletin fixes
  4. For embedded/breadboard implementations, obtain updated firmware from Qualcomm that includes the PlayReady NULL pointer dereference fix and flash the baseband processor
  5. Verify the fix was applied by confirming the security patch level shows 2018-04-05 or later after updating
Caveat Updating to the 2018-04-05 patch level may introduce other behavior changes; test thoroughly on non-production devices first if possible

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

Fix this in Msm8909w Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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