dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2016-10456

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 MDM9206, MDM9607, MDM9615, MDM9635M, MDM9640, MDM9650, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 430, SD 450, SD 600, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 810, SD 820, SD 835, and SDX20, if radish is executed with an interface name set to an invalid interface name, an arbitrary command of 15 characters or less may be executed as a system call.

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 command injection vulnerability exists in the radish utility on affected Qualcomm Snapdragon chipsets. When radish is executed with an invalid interface name parameter, it allows execution of arbitrary system commands (up to 15 characters) with system-level privileges.

MitigationApply the Android security patch level dated 2018-04-05 or later, which contains the vendor fix for this vulnerability. If the device cannot receive this update, consider replacement as this is a firmware-level flaw requiring a vendor-provided patch.

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
Mdm9607 FirmwareOperating system
Affected:all versions
Mdm9615 FirmwareOperating system
Affected:all versions
Mdm9635m FirmwareOperating system
Affected:all versions
Mdm9640 FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions
Msm8909w FirmwareOperating system
Affected:all versions
Sd 210 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. Verify radish utility presence
    Search for the radish binary on the system using 'find / -name radish 2>/dev/null' or check common system paths where utility binaries are stored
    Affected if The radish binary exists on the device, indicating the vulnerable component is present
  2. Confirm chipset and firmware model
    Identify the Qualcomm chipset model and firmware version by checking /proc/version, /proc/cpuinfo, or device-specific firmware information files
    Affected if The chipset/firmware matches any of the affected models: Mdm9206, Mdm9607, Mdm9615, Mdm9635m, Mdm9640, Mdm9650, Msm8909w, or Sd 210
  3. Check Android security patch level
    On Android devices, check the security patch level via 'Settings > About phone > Build number' or by examining /system/build.prop for the 'ro.build.version.security_patch' property
    Affected if The security patch level is earlier than 2018-04-05 or the patch level cannot be determined, indicating the vendor fix has not been applied
  4. Verify radish execution capability
    Attempt to invoke radish with '--help' or check if the binary has execute permissions using 'ls -la [path to radish]'
    Affected if The radish utility is present and executable on the system, making the command injection vector accessible

A device is affected if the radish utility is present on a Qualcomm Snapdragon chipset matching the affected firmware models and the Android security patch level predates the 2018-04-05 vendor fix.

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 Android security patch level dated 2018-04-05 or later, which contains the vendor fix for this vulnerability. If the device cannot receive this update, consider replacement as this is a firmware-level flaw requiring a vendor-provided patch.

Recommended fix Moderate confidence
  1. Contact your device OEM or carrier to obtain the latest firmware update that includes the April 2018 Android Security Bulletin patch for CVE-2016-10456
  2. Verify that the baseband/modem firmware version includes the fix for the radish command injection vulnerability
  3. For devices running Android, ensure the security patch level is April 5, 2018 or later
  4. If your device is no longer supported by the OEM, consider migrating to a supported device as firmware updates will not be provided
Caveat Firmware updates for older devices may not be available; end-of-life devices will require replacement

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

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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