# CVE-2018-5869: Memory corruption in Snapdragon Mobile,Snapdragon Wear

> Improper input validation in QTEE keymaster allows invalid memory access, potentially enabling code execution or privilege escalation on affected 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:** 18 Jan 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-8w83-pffr-jwcc

## What is CVE-2018-5869?

CVE-2018-5869 is a high-severity memory corruption vulnerability in Qualcomm Mdm9206 Firmware, published on 18 Jan 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper input validation in the QTEE keymaster app can lead to invalid memory access in snapdragon mobile and snapdragon wear in versions MDM9206, MDM9607, MSM8909W, SD 210/SD 212/SD 205, SD 410/12, SD 615/16/SD 415, SD 800, SD 810

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2018-5869?

It affects 13 products.


Products: Qualcomm Mdm9206 Firmware, Qualcomm Mdm9607 Firmware, 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 800 Firmware, Qualcomm Sd 810 Firmware.

## How do I fix CVE-2018-5869?

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

## Is CVE-2018-5869 being exploited?

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

## Other vulnerabilities in Qualcomm Mdm9206 Firmware

- [CVE-2016-10394](https://insights.sbomify.com/CVE-2016-10394/): Improper Authentication in Core (critical 9.8)
- [CVE-2019-10522](https://insights.sbomify.com/CVE-2019-10522/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)
- [CVE-2019-10528](https://insights.sbomify.com/CVE-2019-10528/): Use after free in Snapdragon Auto, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)
- [CVE-2019-10533](https://insights.sbomify.com/CVE-2019-10533/): 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-10534](https://insights.sbomify.com/CVE-2019-10534/): Null dereference in Snapdragon Auto, Snapdragon Compute, 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-2018-5869 and fix it if it is affected.

What it is: CVE-2018-5869 is a high-severity memory corruption vulnerability in Qualcomm Mdm9206 Firmware, published on 18 Jan 2019. 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-2018-5869 in the wild and no public exploit code.

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

## Sources

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

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