dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2015-9203

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_set_domainid could lead to a buffer overread.

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 overread vulnerability in the playready_set_domainid function on Qualcomm Snapdragon processors (mobile, automotive, and Wear) results from missing input validation. This allows an attacker to read sensitive memory contents due to the lack of bounds checking on input parameters passed to the function.

MitigationApply Android security patches from April 5, 2018 or later, which contain the fix for this vulnerability. Organizations should identify affected devices in their fleet and ensure OEM/firmware updates are deployed.

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 processor model
    On Android devices, check /proc/cpuinfo or use 'getprop ro.hardware' in adb shell to retrieve the SoC identifier
    Affected if The processor model matches Mdm9206, Mdm9650, Msm8909w, Sd 210, Sd 212, Sd 205, Sd 400, or Sd 410
  2. Check the firmware version
    Retrieve the baseband or firmware version via 'getprop gsm.version.baseband' or 'getprop ro.build.version.firmware' in adb shell
    Affected if The firmware version is any version for the affected models (all versions are listed as vulnerable)
  3. Verify playready DRM is in use
    Check for playready-related libraries or configurations on the device; look for /system/lib/libplayready* or DRM configuration files in /etc or /system/etc
    Affected if Playready DRM functionality is present and the device uses Qualcomm Snapdragon processors from the affected list
  4. Confirm the playready_set_domainid function exists
    Analyze the baseband or DRM firmware binary for the presence of the playready_set_domainid function using strings or binary analysis tools
    Affected if The vulnerable function is present in the firmware

A device is affected if it contains a Qualcomm Snapdragon processor from the affected model list and has playready DRM functionality enabled, as all firmware versions for these models contain the vulnerable function.

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 patches from April 5, 2018 or later, which contain the fix for this vulnerability. Organizations should identify affected devices in their fleet and ensure OEM/firmware updates are deployed.

Recommended fix High confidence

Any Android device update with security patch level dated 2018-04-05 or later (April 2018 security patch level or newer)

  1. Check current Android security patch level on the device (Settings > About Phone > Security patch level)
  2. If the security patch level is earlier than April 5, 2018, apply the latest available Android system update from the device OEM
  3. For enterprise/embedded devices using these specific Qualcomm components (MDM9206, MDM9650, MSM8909W, SD 210/212/205, SD 400, SD 410/12), contact the device manufacturer for firmware updates that incorporate the April 2018 or later Android security patch
  4. After applying the update, verify the security patch level has been updated to May 2018 or later to confirm the vulnerability is patched
Caveat Standard Android update apply risks - ensure backups exist before updating; some older devices may not receive the update if EOL

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

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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