# CVE-2017-18313: Privilege escalation in Snapdragon Mobile, Snapdragon Wear

> Attackers can tamper with authenticated WCNSS firmware via DXE channels, enabling privilege escalation on affected Snapdragon devices.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **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-rhv8-c8mx-v4h4

## What is CVE-2017-18313?

CVE-2017-18313 is a medium-severity vulnerability in Qualcomm Msm8909w 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

Under certain mode of operations, HLOS may be able get direct or indirect access through DXE channels to tamper with the authenticated WCNSS firmware stored in DDR because DXE-accessible memory is located within the authenticated image in Snapdragon Mobile and Snapdragon Wear in version MSM8909W, SD 210/SD 212/SD 205, SD 410/12, SD 615/16/SD 415, SD 617.

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

It affects 10 products.


Products: Qualcomm Msm8909w 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 615 Firmware, Qualcomm Sd 616 Firmware, Qualcomm Sd 617 Firmware.

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

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

## Is CVE-2017-18313 being exploited?

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

## Other vulnerabilities in Qualcomm Msm8909w Firmware

- [CVE-2019-2285](https://insights.sbomify.com/CVE-2019-2285/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)
- [CVE-2019-10509](https://insights.sbomify.com/CVE-2019-10509/): Use after free in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)
- [CVE-2019-10538](https://insights.sbomify.com/CVE-2019-10538/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)
- [CVE-2019-2255](https://insights.sbomify.com/CVE-2019-2255/): Code injection in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)
- [CVE-2019-2259](https://insights.sbomify.com/CVE-2019-2259/): Denial of service in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-18313 is a medium-severity vulnerability in Qualcomm Msm8909w 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-18313 in the wild and no public exploit code.

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

## Sources

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

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