# CVE-2015-9220: Integer overflow in Snapdragon Mobile, Snapdragon Wear

> An integer overflow in Qualcomm Snapdragon firmware allows attackers to execute arbitrary code or escalate privileges via a maliciously encoded firmware image.

- **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-336m-59pm-h599

## What is CVE-2015-9220?

CVE-2015-9220 is a critical vulnerability in Qualcomm Ipq4019 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 and Snapdragon Wear IPQ4019, IPQ8064, MDM9206, MDM9607, MDM9640, MDM9650, QCA4531, QCA6174A, QCA6574AU, QCA6584, QCA6584AU, QCA9377, QCA9378, QCA9379, QCA9558, QCA9880, QCA9886, QCA9980, SD 210/SD 212/SD 205, SD 425, SD 625, SD 810, SD 820, and SDX20, integer overflow occurs when the size of the firmware section is incorrectly encoded in the firmware image.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2015-9220?

It affects 26 products.


Products: Qualcomm Ipq4019 Firmware, Qualcomm Ipq8064 Firmware, Qualcomm Mdm9206 Firmware, Qualcomm Mdm9607 Firmware, Qualcomm Mdm9640 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Qca4531 Firmware, Qualcomm Qca6174a Firmware, Qualcomm Qca6574au Firmware, Qualcomm Qca6584 Firmware, Qualcomm Qca6584au Firmware, Qualcomm Qca9377 Firmware, Qualcomm Qca9378 Firmware, Qualcomm Qca9379 Firmware, Qualcomm Qca9558 Firmware, Qualcomm Qca9880 Firmware, Qualcomm Qca9886 Firmware, Qualcomm Qca9980 Firmware, Qualcomm Sd 205 Firmware, Qualcomm Sd 210 Firmware and 6 more.

## How do I fix CVE-2015-9220?

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

## Is CVE-2015-9220 being exploited?

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

## Other vulnerabilities in Qualcomm Ipq4019 Firmware

- [CVE-2020-11172](https://insights.sbomify.com/CVE-2020-11172/): Memory corruption in Snapdragon Wired Infrastructure and Networking (critical 9.8)
- [CVE-2020-11117](https://insights.sbomify.com/CVE-2020-11117/): Command injection in Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Wired Infrastructure and Networking (critical 9.8)
- [CVE-2014-10045](https://insights.sbomify.com/CVE-2014-10045/): Memory corruption in Snapdragon Mobile, Snapdragon Wear (critical 9.8)
- [CVE-2014-9988](https://insights.sbomify.com/CVE-2014-9988/): Memory corruption in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear (critical 9.8)
- [CVE-2014-9998](https://insights.sbomify.com/CVE-2014-9998/): In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile, Snapdragon Mobile, and Snapdragon Wear IPQ40 (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-9220 and fix it if it is affected.

What it is: CVE-2015-9220 is a critical vulnerability in Qualcomm Ipq4019 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-2015-9220 in the wild and no public exploit code.

Affected product: Qualcomm Ipq4019 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-2015-9220/ (Markdown: https://insights.sbomify.com/CVE-2015-9220/index.md)
```

## Sources

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

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