dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2015-9128

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, and SD 835, lack of validation of the buffer size 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 exists in Qualcomm Snapdragon chipset firmware (multiple generations from MDM9206 to SD 835) due to missing buffer size validation. This memory corruption issue in baseband/modem components could allow remote attackers to execute arbitrary code or cause denial of service.

MitigationApply the April 2018 or later Android security patch level, which contains the vendor fix for this Qualcomm Snapdragon firmware vulnerability. For unpatched or end-of-life devices, 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
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 your device chipset model
    Check the processor/chipset information in device settings under 'About Phone' or 'Hardware Information', or use a terminal command like 'getprop ro.hardware' or 'cat /proc/cpuinfo' to find the Qualcomm Snapdragon model number
    Affected if The chipset matches one of the affected models: MDM9206, MDM9650, MSM8909w, SD 210, SD 212, SD 205, SD 400, or SD 410
  2. Check the baseband/modem firmware version
    In Android settings, go to 'About Phone' > 'Baseband version' or use 'getprop gsm.version.baseband' in a terminal to retrieve the firmware version string
    Affected if The baseband version is present and corresponds to an unpatched firmware build (all versions of the affected chipsets are initially vulnerable)
  3. Verify the Android security patch level
    Go to Settings > About Phone > Android security patch level, or run 'getprop ro.build.version.security_patch' in a terminal to check the installed patch date
    Affected if The security patch level is earlier than April 2018, meaning the vendor fix has not been applied
  4. Confirm the modem/baseband component is active
    Check that the device has cellular connectivity capability and the baseband modem is operational; this can be verified by checking if 'ril.radio.version' or similar radio properties return a value using 'getprop'
    Affected if The device has an active cellular modem with the vulnerable firmware installed (this applies to all affected devices with cellular capability)

You are affected if your device uses any of the listed Qualcomm Snapdragon chipsets (MDM9206, MDM9650, MSM8909w, SD 210, SD 212, SD 205, SD 400, SD 410) and has not received the April 2018 or later Android security update.

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, which contains the vendor fix for this Qualcomm Snapdragon firmware vulnerability. For unpatched or end-of-life devices, consider device replacement.

Recommended fix High confidence

Android Security Patch Level April 2018 or later

  1. Identify the current Android security patch level on the affected device by going to Settings > About Phone > Security Patch Level
  2. Contact the device manufacturer (OEM) to obtain the latest Android security update that includes the April 2018 security patch level or later
  3. Apply the vendor-provided security update to the device
  4. Verify the security patch level has been updated to April 2018 or later after the update completes
Caveat Security patches typically have minimal breaking changes; however, older devices may require Android version upgrades to receive the latest security patches, which could introduce compatibility issues with legacy applications

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
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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