# CVE-2016-10478: Integer overflow in Snapdragon Mobile

> An integer overflow in Qualcomm Snapdragon Mobile's QCRIL SCWS processing leads to a buffer overflow, potentially allowing code execution on Android devices.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Apr 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-www3-83wr-pxc8

## What is CVE-2016-10478?

CVE-2016-10478 is a critical vulnerability in Qualcomm Sd 617 Firmware, published on 18 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In 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.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2016-10478?

It affects 1 product.


Products: Qualcomm Sd 617 Firmware.

## How do I fix CVE-2016-10478?

No fix has been published for CVE-2016-10478 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-10478 being exploited?

There is no known exploitation of CVE-2016-10478 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-10478 and fix it if it is affected.

What it is: CVE-2016-10478 is a critical vulnerability in Qualcomm Sd 617 Firmware, published on 18 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-10478 in the wild and no public exploit code.

Affected product: Qualcomm Sd 617 Firmware. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-10478/ (Markdown: https://insights.sbomify.com/CVE-2016-10478/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-10478
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-10478
- OSV: https://osv.dev/vulnerability/CVE-2016-10478

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-10478/
Summaries are generated and may contain mistakes; the official description above is the record.