dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2016-10492

CRITICAL · 9.1 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, MDM9645, 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 835, SD 845, SD 850, and SDX20, improper ciphersuite validation leads SecSSL accept an unadvertised ciphersuite.

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 Qualcomm's SecSSL library used across multiple Snapdragon and Snapdragon Wear chipsets, improper validation during SSL/TLS cipher suite negotiation allows acceptance of cipher suites that were never advertised by the server. This could enable man-in-the-middle attackers to downgrade connections to weaker cipher suites or bypass security controls.

MitigationApply Android security patch level 2018-04-05 or later to affected devices. This is a firmware-level fix requiring vendor-supplied updates for affected Snapdragon chipset devices.

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

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 /proc/cpuinfo or use 'cat /sys/devices/soc0/soc_id' to retrieve the chipset identifier
    Affected if The chipset matches one of: Mdm9206, Mdm9607, Mdm9615, Mdm9635m, Mdm9640, Mdm9645, Mdm9650, or Msm8909w
  2. Check the firmware version of the chipset
    Query the modem or system firmware version via 'getprop' (e.g., getprop ro.boot.modem) or through /vendor/firmware or /firmware directories
    Affected if Any firmware version is installed on an affected chipset (all versions of listed chipsets are vulnerable)
  3. Confirm SecSSL library presence
    Search for libsecssl.so or secssl in /vendor/lib or /system/lib directories: 'find / -name "*secssl*" 2>/dev/null'
    Affected if The SecSSL library is present on the device, indicating the vulnerable component is in use
  4. Verify SSL/TLS usage
    Monitor network traffic or check if applications use SSL/TLS connections via 'ssltest' or by inspecting app network behavior
    Affected if SSL/TLS connections are established using the SecSSL library on an affected chipset

A device is affected if it contains any of the listed Qualcomm chipsets (Mdm9206, Mdm9607, Mdm9615, Mdm9635m, Mdm9640, Mdm9645, Mdm9650, Msm8909w) running any firmware version and uses the SecSSL library for TLS connections.

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 to affected devices. This is a firmware-level fix requiring vendor-supplied updates for affected Snapdragon chipset devices.

Recommended fix High confidence

Android devices with Security Patch Level 2018-04-05 or later; contact OEM for device-specific updates

  1. Check the current Android security patch level on the device (Settings > About Phone > Security Patch Level)
  2. If the Security Patch Level is earlier than April 5, 2018, apply the latest available Android system update from the device manufacturer or carrier
  3. For MDM9206, MDM9607, MDM9615, MDM9635M, MDM9640, MDM9645, MDM9650, and MSM8909W firmware: contact the device OEM for firmware updates that incorporate the April 2018 Android security patch level
  4. Verify after update that the Security Patch Level shows April 5, 2018 or later
Caveat Users on very old devices or devices no longer supported by OEMs may not receive the update; some legacy devices may not receive patches for this vulnerability

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

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,790
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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