# CVE-2017-18172: Integer overflow in Snapdragon Automobile, Snapdragon Mobile

> An integer overflow in System UI allows attackers to execute arbitrary code or escalate privileges on affected Qualcomm Snapdragon devices.

- **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:** 23 Oct 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-m284-7q72-8635

## What is CVE-2017-18172?

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

### Official description

In a device, with screen size 1440x2560, the check of contiguous buffer will overflow on certain buffer size resulting in an Integer Overflow or Wraparound in System UI in Snapdragon Automobile, Snapdragon Mobile in version MDM9635M, SD 400, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 800, SD 810, SD 820, SD 820A, SD 835, SDM630, SDM636, SDM660, Snapdragon_High_Med_2016.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 24 products.


Products: Qualcomm Mdm9635m Firmware, Qualcomm Sd 400 Firmware, Qualcomm Sd 410 Firmware, Qualcomm Sd 412 Firmware, Qualcomm Sd 415 Firmware, Qualcomm Sd 425 Firmware, Qualcomm Sd 427 Firmware, Qualcomm Sd 430 Firmware, Qualcomm Sd 435 Firmware, Qualcomm Sd 450 Firmware, Qualcomm Sd 615 Firmware, Qualcomm Sd 616 Firmware, Qualcomm Sd 617 Firmware, Qualcomm Sd 625 Firmware, Qualcomm Sd 650 Firmware, Qualcomm Sd 652 Firmware, Qualcomm Sd 800 Firmware, Qualcomm Sd 810 Firmware, Qualcomm Sd 820 Firmware, Qualcomm Sd 820a Firmware and 4 more.

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

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

## Is CVE-2017-18172 being exploited?

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

## Other vulnerabilities in Qualcomm Mdm9635m Firmware

- [CVE-2017-18160](https://insights.sbomify.com/CVE-2017-18160/): Hardcoded credentials in Snapdragon Mobile, Snapdragon Wear (critical 9.8)
- [CVE-2014-9985](https://insights.sbomify.com/CVE-2014-9985/): Race condition in Snapdragon Mobile (critical 9.8)
- [CVE-2016-10494](https://insights.sbomify.com/CVE-2016-10494/): Integer overflow in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear (critical 9.8)
- [CVE-2016-10495](https://insights.sbomify.com/CVE-2016-10495/): Integer overflow in Snapdragon Mobile (critical 9.8)
- [CVE-2016-10496](https://insights.sbomify.com/CVE-2016-10496/): Null dereference in Snapdragon Mobile (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-18172 is a high-severity vulnerability in Qualcomm Mdm9635m Firmware, published on 23 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-18172 in the wild and no public exploit code.

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

## Sources

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

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