CVE-2016-10478
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 · uneditedIn Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile SD 617, incorrect size calculation in QCRIL SCWS processing have Integer overflow which will lead to a buffer overflow.
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 confidenceInteger overflow in QCRIL SCWS size calculation on Qualcomm Snapdragon SD 617 leads to buffer overflow. This vulnerability in the Qualcomm Common RIL (Radio Interface Layer) subsystem allows potential arbitrary code execution or denial of service via malformed SCWS messages.
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 dataall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify device chipsetCheck the device specifications or use system information tools (e.g., 'cat /proc/cpuinfo' or settings > About Phone) to determine if the device uses Qualcomm Snapdragon SD 617 processorAffected if Device hardware contains Qualcomm Snapdragon SD 617 chipset
-
Check Android security patch levelNavigate to Settings > About Phone > Android security patch level, or run 'getprop ro.build.version.security_patch' via ADBAffected if Security patch level is earlier than 2018-04-05 or not displayed/available
-
Verify baseband firmware versionCheck modem/baseband firmware version via 'getprop gsm.version.baseband' or Settings > About Phone > Baseband versionAffected if Baseband version cannot be determined or is from an unpatched firmware build
User is affected if the device contains Qualcomm Snapdragon SD 617 chipset AND has an Android security patch level earlier than April 5, 2018.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply Android security patch level dated 2018-04-05 or later to affected devices. If patches unavailable from device OEM, consider network-based controls to limit exposure of vulnerable telephony interfaces.
Android security patch level after 2018-04-05 (device-specific firmware update from manufacturer)
- Identify the device manufacturer and model using the affected Qualcomm Snapdragon SD 617 SoC
- Contact the device manufacturer or carrier for the latest firmware update
- Apply the manufacturer-provided Android security patch update that addresses CVE-2016-10478
- Verify the device is running Android security patch level after 2018-04-05
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10478 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-10478 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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