# CVE-2020-11164: Missing authorization in Snapdragon Auto, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables

> Third-party apps can trigger privileged broadcasts in Perfdump due to improper access control, leading to privilege escalation on Qualcomm Snapdragon devices.

- **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:** 2 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-v7xc-6mwj-7f9m

## What is CVE-2020-11164?

CVE-2020-11164 is a high-severity missing authorization vulnerability in Qualcomm Apq8096au Firmware, published on 2 Nov 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

u'Third-party app may also call the broadcasts in Perfdump and cause privilege escalation issue due to improper access control' in Snapdragon Auto, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables in Agatti, APQ8096AU, APQ8098, Bitra, Kamorta, MSM8909W, MSM8917, MSM8940, Nicobar, QCA6390, QCM2150, QCS605, Rennell, SA6155P, SA8155P, Saipan, SDA660, SDM429W, SDM450, SDM630, SDM636, SDM660, SDM670, SDM710, SM6150, SM7150, SM8150, SM8250, SXR1130, SXR2130

## Which versions are affected by CVE-2020-11164?

It affects 30 products.


Products: Qualcomm Agatti Firmware, Qualcomm Apq8096au Firmware, Qualcomm Apq8098 Firmware, Qualcomm Bitra Firmware, Qualcomm Kamorta Firmware, Qualcomm Msm8909w Firmware, Qualcomm Msm8917 Firmware, Qualcomm Msm8940 Firmware, Qualcomm Nicobar Firmware, Qualcomm Qca6390 Firmware, Qualcomm Qcm2150 Firmware, Qualcomm Qcs605 Firmware, Qualcomm Rennell Firmware, Qualcomm Sa6155p Firmware, Qualcomm Sa8155p Firmware, Qualcomm Saipan Firmware, Qualcomm Sda660 Firmware, Qualcomm Sdm429w Firmware, Qualcomm Sdm450 Firmware, Qualcomm Sdm630 Firmware and 10 more.

## How do I fix CVE-2020-11164?

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

## Is CVE-2020-11164 being exploited?

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

## Other vulnerabilities in Qualcomm Apq8096au Firmware

- [CVE-2020-3654](https://insights.sbomify.com/CVE-2020-3654/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables (critical 9.8)
- [CVE-2020-3673](https://insights.sbomify.com/CVE-2020-3673/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables (critical 9.8)
- [CVE-2020-3692](https://insights.sbomify.com/CVE-2020-3692/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile (critical 9.8)
- [CVE-2020-3670](https://insights.sbomify.com/CVE-2020-3670/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables (critical 9.1)
- [CVE-2020-11125](https://insights.sbomify.com/CVE-2020-11125/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-11164 and fix it if it is affected.

What it is: CVE-2020-11164 is a high-severity missing authorization vulnerability in Qualcomm Apq8096au Firmware, published on 2 Nov 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-2020-11164 in the wild and no public exploit code.

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

## Sources

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

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