dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2016-10414

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 Small Cell SoC, Snapdragon Automobile, Snapdragon Mobile, and Snapdragon Wear FSM9055, IPQ4019, MDM9206, MDM9607, MDM9625, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, 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, SD 850, and SDX20, when a hash is passed with zero datalength, the code returns an error, even though zero data length is valid.

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

In affected Qualcomm chipsets, a logic error in hash validation causes the system to return an error when processing hashes with zero data length, despite zero-length data being a valid input. This could allow attackers to cause denial of service or potentially bypass security controls by manipulating hash operations.

MitigationApply the April 2018 or later security patch level to affected devices; contact device OEMs for firmware updates addressing this vulnerability in Snapdragon chipset firmware.

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
Mdm9625 FirmwareOperating system
Affected:all versions
Mdm9635m FirmwareOperating system
Affected:all versions
Mdm9640 FirmwareOperating system
Affected:all versions
Mdm9645 FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions
Mdm9655 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 the device hardware specifications or use AT commands (e.g., AT+QCFG="nw" or AT+CGMM) to query the modem chipset model
    Affected if The chipset is not one of the listed affected models (Mdm9206, Mdm9607, Mdm9625, Mdm9635m, Mdm9640, Mdm9645, Mdm9650, Mdm9655)
  2. Confirm firmware version
    Query the firmware version using AT commands such as AT+CGMR or AT+QVER
    Affected if The chipset is one of the affected models and runs any firmware version (all versions are affected)
  3. Check security patch level
    Query the Android security patch level via Settings > About Phone > Security Patch Level, or use 'getprop ro.build.version.security_patch' via ADB
    Affected if The security patch level is earlier than April 2018 and the chipset is one of the affected models

A device is affected if it contains one of the listed Qualcomm modem chipsets (Mdm9206, Mdm9607, Mdm9625, Mdm9635m, Mdm9640, Mdm9645, Mdm9650, Mdm9655) with any firmware version and has a security patch level earlier than 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 or later security patch level to affected devices; contact device OEMs for firmware updates addressing this vulnerability in Snapdragon chipset firmware.

Recommended fix High confidence

Android security patch level May 2018 or later (containing Qualcomm fix for hash zero-length handling)

  1. Identify your device model and carrier (if applicable)
  2. Check current Android security patch level in Settings > About Phone > Security patch level
  3. Ensure the security patch level is May 2018 or later (which includes the April 5, 2018 fix)
  4. If not updated, check for system updates from your device manufacturer
  5. If no update available, contact your device manufacturer or carrier for firmware update availability
  6. Apply any available firmware/modem updates from Qualcomm through manufacturer channels
Caveat Firmware updates may have compatibility considerations; ensure backup before updating

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
  • Implementation40.0 h
  • Testing24.0 h
  • Review / QA8.0 h
80.0 hours of engineering $13,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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