# CVE-2017-18171: Memory corruption in Snapdragon Mobile

> Improper input validation in Bluetooth Controller allows memory corruption, potentially enabling code execution or privilege escalation on Snapdragon devices.

- **Severity:** High 8.8 (`CVSS:3.0/AV:A/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:** 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-9h9q-wf3q-v458

## What is CVE-2017-18171?

CVE-2017-18171 is a high-severity memory corruption vulnerability in Qualcomm Qca9379 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

Improper input validation for GATT data packet received in Bluetooth Controller function can lead to possible memory corruption in Snapdragon Mobile in version QCA9379, SD 210/SD 212/SD 205, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 450, SD 615/16/SD 415, SD 625, SD 650/52, SD 820, SD 835, SD 845, SD 850, SDM630, SDM636, SDM660, SDM710, Snapdragon_High_Med_2016.

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

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

It affects 25 products.


Products: Qualcomm Qca9379 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 427 Firmware, Qualcomm Sd 430 Firmware, Qualcomm Sd 435 Firmware, Qualcomm Sd 450 Firmware, Qualcomm Sd 615 Firmware, Qualcomm Sd 616 Firmware, Qualcomm Sd 625 Firmware, Qualcomm Sd 650 Firmware, Qualcomm Sd 652 Firmware, Qualcomm Sd 820 Firmware, Qualcomm Sd 835 Firmware, Qualcomm Sd 845 Firmware and 5 more.

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

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

## Is CVE-2017-18171 being exploited?

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

## Other vulnerabilities in Qualcomm Qca9379 Firmware

- [CVE-2017-18170](https://insights.sbomify.com/CVE-2017-18170/): Memory corruption in Snapdragon Mobile (high 8.8)
- [CVE-2017-18283](https://insights.sbomify.com/CVE-2017-18283/): Memory corruption in Snapdragon Mobile (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-18171 is a high-severity memory corruption vulnerability in Qualcomm Qca9379 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-18171 in the wild and no public exploit code.

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

## Sources

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

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