# CVE-2016-10418: Missing authorization in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear

> Improper access control in Qualcomm Snapdragon firmware allows enabling PMIC debug features, bypassing security restrictions.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Apr 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-8cvm-w7gh-qfmq

## What is CVE-2016-10418?

CVE-2016-10418 is a high-severity missing authorization vulnerability in Qualcomm Mdm9206 Firmware, published on 18 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile, Snapdragon Mobile, and Snapdragon Wear MDM9206, MDM9650, SD 210/SD 212/SD 205, SD 425, SD 430, SD 450, SD 625, SD 650/52, SD 820, SD 820A, and SD 835, HLOS can enable PMIC debug through TCSR_QPDI_DISABLE_CFG due to improper access control.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2016-10418?

It affects 14 products.


Products: Qualcomm Mdm9206 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Sd 205 Firmware, Qualcomm Sd 210 Firmware, Qualcomm Sd 212 Firmware, Qualcomm Sd 425 Firmware, Qualcomm Sd 430 Firmware, Qualcomm Sd 450 Firmware, Qualcomm Sd 625 Firmware, Qualcomm Sd 650 Firmware, Qualcomm Sd 652 Firmware, Qualcomm Sd 820 Firmware, Qualcomm Sd 820a Firmware, Qualcomm Sd 835 Firmware.

## How do I fix CVE-2016-10418?

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

## Is CVE-2016-10418 being exploited?

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

What it is: CVE-2016-10418 is a high-severity missing authorization vulnerability in Qualcomm Mdm9206 Firmware, published on 18 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-10418 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-2016-10418/ (Markdown: https://insights.sbomify.com/CVE-2016-10418/index.md)
```

## Sources

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

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