dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2016-10476

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, 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, and SDX20, missing array index checks on app index in function qcril_uim_clear_encrypted_pin results in accessing addresses outside the bounds of the buffer when app index is too large.

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 array bounds checking in the qcril_uim_clear_encrypted_pin function on Qualcomm Snapdragon chipsets allows out-of-bounds memory access when an app index exceeds buffer boundaries. This is a buffer over-read vulnerability in the UIM (SIM card) subsystem of the Qualcomm RIL (Radio Interface Layer) firmware.

MitigationApply the Android security patch from 2018-04-05 or later, which includes proper bounds checking in the affected function. Device manufacturers must push firmware updates to users of affected Snapdragon 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
Mdm9650 FirmwareOperating system
Affected:all versions
Msm8909w 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

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 device chipset model
    Check the device specifications or system information to determine the Qualcomm Snapdragon chipset model (e.g., Mdm9206, Mdm9607, Mdm9650, Msm8909w, Sd 210, Sd 212, Sd 205, Sd 400)
    Affected if The chipset matches one of the affected models: Mdm9206, Mdm9607, Mdm9650, Msm8909w, Sd 210, Sd 212, Sd 205, or Sd 400
  2. Verify the RIL firmware version
    Access the Qualcomm RIL (Radio Interface Layer) firmware version through device diagnostics, engineering mode, or AT command interface if available
    Affected if The RIL firmware version corresponds to any version of the affected chipsets (all versions listed are vulnerable)
  3. Confirm the UIM subsystem is active
    Check if the device has UIM/SIM card functionality enabled and the SIM card subsystem is operational
    Affected if The device has an active SIM card interface and uses the Qualcomm UIM subsystem, which contains the vulnerable qcril_uim_clear_encrypted_pin function
  4. Check for the vulnerable function in firmware
    Analyze the RIL firmware binary or kernel logs for the presence of the qcril_uim_clear_encrypted_pin function if firmware dumping is possible
    Affected if The function qcril_uim_clear_encrypted_pin exists in the firmware without proper bounds checking

A device is affected if it uses any of the listed Qualcomm Snapdragon chipsets (Mdm9206, Mdm9607, Mdm9650, Msm8909w, Sd 210, Sd 212, Sd 205, or Sd 400) with the vulnerable RIL/UIM firmware, as all versions of these chipsets contain the flaw.

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 from 2018-04-05 or later, which includes proper bounds checking in the affected function. Device manufacturers must push firmware updates to users of affected Snapdragon devices.

Recommended fix Moderate confidence
  1. Contact your device OEM (Original Equipment Manufacturer) to obtain the latest firmware update for your specific device model
  2. Verify the Android security patch level on your device (Settings > About Phone > Security patch level)
  3. Ensure the security patch level is April 5, 2018 or later, as this CVE was addressed in the 2018-04-05 Android security bulletin
  4. If no update is available from your OEM, consider replacing the device or contacting Qualcomm directly for chipset-level patches
  5. For embedded/IoT devices using these modems, contact the device manufacturer for firmware updates specific to the MDM9206, MDM9607, MDM9650, MSM8909W, SD 210, SD 212, SD 205, or SD 400 modules
Caveat Firmware updates for embedded modem components may require professional installation and could void device warranties if not performed by the OEM

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
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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