dbcve.org
Mdm9645 FirmwareOperating system · Qualcomm

CVE-2015-9142

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 MDM9645, MDM9650, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 450, SD 615/16/SD 415, SD 625, SD 650/52, SD 800, SD 808, SD 810, SD 820, SDM630, SDM636, SDM660, and Snapdragon_High_Med_2016, bounds check is missing for vtable index in DAL-TO-QDI conversion framework.

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

Missing bounds check on vtable index in the DAL-TO-QDI conversion framework on Qualcomm Snapdragon chipsets allows potential memory corruption leading to arbitrary code execution or denial of service. The vulnerability exists in the interface between the Device Abstraction Layer and Qualcomm Debug Interface.

MitigationApply Android security patch level 2018-04-05 or later, which includes Qualcomm-provided firmware updates. Verify device manufacturers have released and installed the appropriate patch for affected Snapdragon variants.

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
Mdm9645 FirmwareOperating system
Affected:all versions
Mdm9650 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

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 chipset model
    Check device specifications or use commands like 'getprop ro.board.platform' or 'getprop ro.product.device' to identify the Snapdragon variant. For Android devices, check Settings > About Phone > Chipset or Model details.
    Affected if The device uses any of these affected chipsets: Mdm9645, Mdm9650, SD 210, SD 212, SD 205, SD 400, SD 410, or SD 412.
  2. Check the baseband or firmware version
    On Android, go to Settings > About Phone > Baseband version, or use 'getprop' commands like 'getprop gsm.version.baseband' or 'getprop ro.build.version.baseband' to retrieve the firmware version string.
    Affected if The firmware version cannot be verified as patched, since all versions of these chipsets were affected prior to the 2018-04-05 patch.
  3. Verify the Android security patch level
    On Android, go to Settings > About Phone > Android security patch level, or use 'getprop ro.build.version.security_patch' to retrieve the patch date.
    Affected if The security patch level is earlier than 2018-04-05 or cannot be determined, indicating the vulnerability has not been addressed.
  4. Check for manufacturer firmware updates
    Contact the device manufacturer or check their support website to confirm whether a firmware update addressing this CVE has been released and installed for your specific device model.
    Affected if The manufacturer has not released or installed a firmware update for the specific Snapdragon variant in the device.

The device is affected if it contains any of the listed Qualcomm chipsets (Mdm9645, Mdm9650, SD 210/212/205/400/410/412) and the Android security patch level is earlier than 2018-04-05 or the firmware has not been updated by the manufacturer.

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 patch level 2018-04-05 or later, which includes Qualcomm-provided firmware updates. Verify device manufacturers have released and installed the appropriate patch for affected Snapdragon variants.

Recommended fix High confidence

Android Security Patch Level 2018-04-05 or later

  1. Verify the current Android security patch level on the device through Settings > About Phone > Security Patch Level
  2. Update the device to Android security patch level 2018-04-05 or later via carrier or OEM firmware update
  3. If the device manufacturer no longer provides updates, consider migrating to a newer device that receives regular security patches
  4. For embedded/IoT devices using these Snapdragon variants, contact the device manufacturer for firmware updates incorporating the April 2018 security patch
Caveat Devices no longer supported by OEMs may not receive this update; legacy device replacement may be required

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

Fix this in Mdm9645 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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