# CVE-2019-14116: Privilege escalation in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking

> Attackers can escalate privileges by exploiting disabled XPU protections during crash dump boot flows in Qualcomm Snapdragon chipsets.

- **Severity:** High 7.8 (`CVSS:3.1/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:** 16 Apr 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-j9r4-wggr-vqrx

## What is CVE-2019-14116?

CVE-2019-14116 is a high-severity vulnerability in Qualcomm Ipq6018 Firmware, published on 16 Apr 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Privilege escalation by using an altered debug policy image can occur as the XPU protecting the debug policy regions are disabled during the crash dump boot flow in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking in IPQ6018

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2019-14116?

It affects 1 product.


Products: Qualcomm Ipq6018 Firmware.

## How do I fix CVE-2019-14116?

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

## Is CVE-2019-14116 being exploited?

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

## Other vulnerabilities in Qualcomm Ipq6018 Firmware

- [CVE-2020-3668](https://insights.sbomify.com/CVE-2020-3668/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking (critical 9.8)
- [CVE-2019-14111](https://insights.sbomify.com/CVE-2019-14111/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking (critical 9.8)
- [CVE-2019-10562](https://insights.sbomify.com/CVE-2019-10562/): Auth bypass in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking (high 7.8)
- [CVE-2019-10597](https://insights.sbomify.com/CVE-2019-10597/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking (high 7.8)
- [CVE-2020-3618](https://insights.sbomify.com/CVE-2020-3618/): Null dereference in Snapdragon Compute, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-14116 and fix it if it is affected.

What it is: CVE-2019-14116 is a high-severity vulnerability in Qualcomm Ipq6018 Firmware, published on 16 Apr 2020. 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-2019-14116 in the wild and no public exploit code.

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

## Sources

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

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