dbcve.org
Sd 210 FirmwareOperating system · Qualcomm

CVE-2016-10477

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 SD 210/SD 212/SD 205, SD 400, SD 430, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 810, and SD 820, while processing smart card requests, a buffer overflow can occur.

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 buffer overflow vulnerability exists in the smart card processing subsystem of multiple Qualcomm Snapdragon mobile processors (SD 210/212/205 through SD 820). The flaw allows memory corruption during smart card request handling, which can lead to arbitrary code execution or privilege escalation due to the critical nature of smart card operations.

MitigationApply Android security patch level April 2018 or later, which contains the vendor-supplied fix for this vulnerability in the affected Snapdragon baseband/processor 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
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
Sd 430 FirmwareOperating system
Affected:all versions
Sd 615 FirmwareOperating system
Affected:all versions
Sd 616 FirmwareOperating system
Affected:all versions
Sd 415 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 Snapdragon processor model
    Retrieve the processor/model information from the device (via Settings > About Phone, or system logs, or /proc/cpuinfo on rooted devices)
    Affected if The identified model matches SD 210, SD 212, SD 205, SD 400, SD 430, SD 615, SD 616, or SD 415
  2. Confirm smart card functionality is in use
    Determine whether the device utilizes smart card operations - this includes SIM card access, eSIM provisioning, or any application that interacts with the SIM/Smart Card subsystem (check running services, SIM status in Settings, or modem logs)
    Affected if Smart card/SIM functionality is actively used or accessible on the device
  3. Check Android security patch level
    View the Android security patch level (Settings > About Phone > Security Patch Level, or via getprop ro.build.version.security_patch)
    Affected if The security patch level is earlier than April 2018, indicating the vendor fix has not been applied

The device is affected if it uses a listed Snapdragon model (SD 210/212/205/400/430/615/616/415), has smart card functionality enabled, and has not received the April 2018 or later Android security patch.

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 April 2018 or later, which contains the vendor-supplied fix for this vulnerability in the affected Snapdragon baseband/processor firmware.

Recommended fix Moderate confidence

Android security patch level April 5, 2018 or later (April 2018 security bulletin)

  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, check for available system/firmware updates from the device manufacturer
  3. Apply all available Android security updates. The vulnerability was patched in the Android security bulletin for April 2018 (or later security patch levels)
  4. After updating, verify the security patch level shows April 5, 2018 or later
  5. If the device manufacturer no longer provides updates, consider migrating to a device that still receives security patches
  6. For enterprise/embedded deployments, contact the device original equipment manufacturer (OEM) for firmware-level updates specific to the Snapdragon chipset
Caveat Some older devices may no longer receive security updates from manufacturers; legacy devices may need replacement

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

Fix this in Sd 210 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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