# CVE-2018-5884: Privilege escalation in Snapdragon Mobile, Snapdragon Wear

> Improper access control allows non-standard applications to acquire permissions for Qualcomm-specific proprietary intents, leading to privilege escalation.

- **Severity:** High 8.4 (`CVSS:3.0/AV:L/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:** 6 Jul 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-6fjp-j9rq-frm5

## What is CVE-2018-5884?

CVE-2018-5884 is a high-severity vulnerability in Qualcomm Mdm9206 Firmware, published on 6 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper Access Control in Multimedia in Snapdragon Mobile and Snapdragon Wear, Non-standard applications without permission may acquire permission of Qualcomm-specific proprietary intents.

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 12 products.


Products: Qualcomm Mdm9206 Firmware, Qualcomm Mdm9607 Firmware, Qualcomm Mdm9635m Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Sd 205 Firmware, Qualcomm Sd 210 Firmware, Qualcomm Sd 212 Firmware, Qualcomm Sd 415 Firmware, Qualcomm Sd 615 Firmware, Qualcomm Sd 616 Firmware, Qualcomm Sd 625 Firmware, Qualcomm Sd 835 Firmware.

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

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

## Is CVE-2018-5884 being exploited?

There is no known exploitation of CVE-2018-5884 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-5884 and fix it if it is affected.

What it is: CVE-2018-5884 is a high-severity vulnerability in Qualcomm Mdm9206 Firmware, published on 6 Jul 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-2018-5884 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-5884/ (Markdown: https://insights.sbomify.com/CVE-2018-5884/index.md)
```

## Sources

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

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