dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2016-10466

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, 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 835, SD 845, SD 850, and SDX20, during SSL handshake, if RNG function (crypto API) returns error, SSL uses hard-coded random value.

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 vulnerable Qualcomm Snapdragon chipsets, during SSL/TLS handshake, if the hardware Random Number Generator (RNG) from the crypto API returns an error or fails, the SSL implementation falls back to using a hard-coded static random value instead of properly handling the error. This completely undermines the cryptographic security of the SSL connection since predictable values replace proper randomness.

MitigationApply the Android security patch level from 2018-04-05 or later, which contains the Qualcomm firmware fix that ensures SSL properly handles RNG errors instead of using hard-coded values.

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 Snapdragon chipset model
    Check the device specifications or system information to determine the chipset model (e.g., Mdm9206, Mdm9607, Mdm9625, Mdm9635m, Mdm9640, Mdm9645, Mdm9650, or Mdm9655)
    Affected if The device uses any of the listed affected chipset models (Mdm9206, Mdm9607, Mdm9625, Mdm9635m, Mdm9640, Mdm9645, Mdm9650, or Mdm9655)
  2. Check the baseband firmware version
    Access the baseband or modem firmware information through the device settings or by querying the radio interface layer (e.g., via AT commands or system diagnostic tools)
    Affected if The baseband firmware version corresponds to the affected chipset and the patch level is not applied
  3. Verify the Android security patch level
    Go to Settings > About Phone > Android security patch level, or run 'adb shell getprop ro.build.version.security_patch'
    Affected if The Android security patch level is earlier than 2018-04-05, indicating the fix is not applied
  4. Confirm SSL/TLS library in use
    Identify if the device uses the vulnerable Qualcomm SSL implementation for TLS handshakes by examining the SSL library or crypto provider in use
    Affected if The device relies on the Qualcomm crypto API and its SSL implementation that performs the faulty RNG fallback

A device is affected if it contains any of the listed Qualcomm Snapdragon chipsets (Mdm9206, Mdm9607, Mdm9625, Mdm9635m, Mdm9640, Mdm9645, Mdm9650, or Mdm9655) and has an Android security patch level earlier than 2018-04-05.

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 from 2018-04-05 or later, which contains the Qualcomm firmware fix that ensures SSL properly handles RNG errors instead of using hard-coded values.

Recommended fix High confidence

Android Security Patch Level April 2018 or later (containing Qualcomm modem firmware fix)

  1. Apply the latest Android security patch level from your device manufacturer. This vulnerability was addressed in the April 2018 Android Security Patch Level.
  2. Verify the installed security patch level on the device by going to Settings > About Phone > Security Patch Level. Ensure the date is April 5, 2018 or later.
  3. If your device manufacturer has not released an update containing the April 2018 security patch, contact the device manufacturer for further guidance and timeline for remediation.
  4. For enterprise or embedded deployments using these Qualcomm modem components, contact Qualcomm or the original equipment manufacturer (OEM) for specific firmware updates addressing CVE-2016-10466.
Caveat Users should ensure their device supports the target security patch level; older devices may no longer receive updates

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
  • Testing16.0 h
  • Review / QA8.0 h
32.0 hours of engineering $5,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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