# CVE-2017-18124: Integer overflow in Small Cell SoC, Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear

> An integer overflow in Qualcomm Snapdragon SoC secure boot allows attackers to potentially execute arbitrary code or escalate privileges.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Oct 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-ccf4-6hm9-2rqc

## What is CVE-2017-18124?

CVE-2017-18124 is a high-severity vulnerability in Qualcomm Ipq4019 Firmware, published on 26 Oct 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

During secure boot, addition is performed on uint8 ptrs which led to overflow issue in Small Cell SoC, Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear in version FSM9055, IPQ4019, MDM9206, MDM9607, MDM9625, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8909W, MSM8996AU, SD 210/SD 212/SD 205, SD 410/12, SD 425, SD 430, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 800, SD 810, SD 820, SD 820A, SD 835, SD 845, SD 850, SDA660, SDX20

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2017-18124?

It affects 36 products.


Products: Qualcomm Fsm9055 Firmware, Qualcomm Ipq4019 Firmware, Qualcomm Mdm9206 Firmware, Qualcomm Mdm9607 Firmware, Qualcomm Mdm9625 Firmware, Qualcomm Mdm9635m Firmware, Qualcomm Mdm9640 Firmware, Qualcomm Mdm9645 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Mdm9655 Firmware, Qualcomm Msm8909w Firmware, Qualcomm Msm8996au Firmware, Qualcomm Sd 205 Firmware, Qualcomm Sd 210 Firmware, Qualcomm Sd 212 Firmware, Qualcomm Sd 410 Firmware, Qualcomm Sd 412 Firmware, Qualcomm Sd 415 Firmware, Qualcomm Sd 425 Firmware, Qualcomm Sd 430 Firmware and 16 more.

## How do I fix CVE-2017-18124?

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

## Is CVE-2017-18124 being exploited?

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

## Other vulnerabilities in Qualcomm Ipq4019 Firmware

- [CVE-2014-10052](https://insights.sbomify.com/CVE-2014-10052/): Information disclosure in Snapdragon Mobile, Snapdragon Wear, Small Cell SoC (critical 9.8)
- [CVE-2015-9138](https://insights.sbomify.com/CVE-2015-9138/): Memory corruption in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear, Small Cell SoC (critical 9.8)
- [CVE-2015-9196](https://insights.sbomify.com/CVE-2015-9196/): Privilege escalation in Snapdragon Mobile, Small Cell SoC (critical 9.8)
- [CVE-2015-9224](https://insights.sbomify.com/CVE-2015-9224/): Memory corruption in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear, Small Cell SoC (critical 9.8)
- [CVE-2016-10412](https://insights.sbomify.com/CVE-2016-10412/): Integer overflow in Small Cell SoC , Snapdragon Mobile, Snapdragon Wear (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-18124 and fix it if it is affected.

What it is: CVE-2017-18124 is a high-severity vulnerability in Qualcomm Ipq4019 Firmware, published on 26 Oct 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-18124 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-2017-18124/ (Markdown: https://insights.sbomify.com/CVE-2017-18124/index.md)
```

## Sources

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

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