dbcve.org
Sd 210 FirmwareOperating system · Qualcomm

CVE-2016-10407

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 410/12, SD 430, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 810, SD 820, and SD 835, an integer overflow leading to buffer overflow can occur during a VT call.

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

An integer overflow vulnerability in the Video Telephony (VT) call processing component of affected Qualcomm Snapdragon chipsets allows remote attackers to cause a buffer overflow. Successful exploitation could lead to remote code execution or denial of service. The vulnerability exists in the VT call handling routine where integer overflow checks are insufficient before buffer allocation.

MitigationApply the Android security patch level released on or after April 5, 2018, which contains the fix for this vulnerability. If patches are unavailable from the device OEM, implement network-level controls to limit exposure to untrusted VT call traffic.

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 410 FirmwareOperating system
Affected:all versions
Sd 412 FirmwareOperating system
Affected:all versions
Sd 430 FirmwareOperating system
Affected:all versions
Sd 450 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 device specifications, system information, or use AT command 'AT+QCFG="nw_config"' or 'AT+CGMM' to query the modem firmware and identify the chipset variant (Sd 210, Sd 212, Sd 205, Sd 400, Sd 410, Sd 412, Sd 430, or Sd 450)
    Affected if The device uses any of the listed affected chipsets: Sd 210, Sd 212, Sd 205, Sd 400, Sd 410, Sd 412, Sd 430, or Sd 450
  2. Verify Video Telephony feature status
    Check device phone settings under 'Video Call' or 'VT' settings, or query the modem via AT command to determine if Video Telephony is enabled and operational on the device
    Affected if Video Telephony (VT) feature is enabled on the device
  3. Check firmware version against patch date
    Query the modem firmware version using AT command 'AT+CGMR' or through Android system information. Compare the firmware version and security patch level against the April 5, 2018 patch date
    Affected if The firmware is from before April 5, 2018 and no security patch containing the fix has been applied
  4. Confirm VT call handling is accessible
    Determine if the device can receive or place Video Telephony calls from untrusted sources, as the vulnerability is triggered during VT call processing
    Affected if The device can process incoming VT calls from potentially untrusted sources

A device is affected if it uses any of the listed Qualcomm Snapdragon chipsets (Sd 210/212/205/400/410/412/430/450), has Video Telephony enabled, and is running firmware without the April 5, 2018 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 the Android security patch level released on or after April 5, 2018, which contains the fix for this vulnerability. If patches are unavailable from the device OEM, implement network-level controls to limit exposure to untrusted VT call traffic.

Recommended fix High confidence

Android Security Patch Level 2018-04-05 or later (contact device vendor for specific firmware version)

  1. Check your device's current Android security patch level in Settings > About Phone > Android security patch level
  2. If the security patch level is earlier than April 5, 2018, your device is vulnerable
  3. Contact your device manufacturer (OEM) for the latest security update that includes the April 2018 Android security patch or later
  4. Apply the vendor-provided security update through Settings > System > Software Update or Settings > About Phone > System Updates
  5. Verify after updating that the Android security patch level shows April 2018 or later

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

Fix this in Sd 210 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing20.0 h
  • Review / QA8.0 h
40.0 hours of engineering $6,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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