# CVE-2020-11161: Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music

> Out-of-bounds memory access in Qualcomm Snapdragon components allows attackers to potentially execute code or cause denial of service via negative width calculations.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:** 9 Jun 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-cr6c-2fj6-gjp2

## What is CVE-2020-11161?

CVE-2020-11161 is a high-severity memory corruption vulnerability in Qualcomm Apq8053 Firmware, published on 9 Jun 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Out-of-bounds memory access can occur while calculating alignment requirements for a negative width from external components in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 226 products.


Products: Qualcomm Apq8053 Firmware, Qualcomm Apq8064au Firmware, Qualcomm Apq8096au Firmware, Qualcomm Ar8031 Firmware, Qualcomm Ar8151 Firmware, Qualcomm Csra6620 Firmware, Qualcomm Csra6640 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Msm8996au Firmware, Qualcomm Pm215 Firmware, Qualcomm Pm3003a Firmware, Qualcomm Pm6125 Firmware, Qualcomm Pm6150 Firmware, Qualcomm Pm6150l Firmware, Qualcomm Pm670 Firmware, Qualcomm Pm670a Firmware, Qualcomm Pm670l Firmware, Qualcomm Pm7350c Firmware, Qualcomm Pm8005 Firmware, Qualcomm Pm8008 Firmware and 206 more.

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

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

## Is CVE-2020-11161 being exploited?

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

## Other vulnerabilities in Qualcomm Apq8053 Firmware

- [CVE-2022-22071](https://insights.sbomify.com/CVE-2022-22071/): Qualcomm Multiple Chipsets Use-After-Free (high 8.4, exploited in the wild)
- [CVE-2020-11153](https://insights.sbomify.com/CVE-2020-11153/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile (critical 9.8)
- [CVE-2020-3703](https://insights.sbomify.com/CVE-2020-3703/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music (critical 9.8)
- [CVE-2019-14080](https://insights.sbomify.com/CVE-2019-14080/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables (critical 9.8)
- [CVE-2020-3628](https://insights.sbomify.com/CVE-2020-3628/): Information disclosure in Snapdragon Consumer IOT, Snapdragon Mobile (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-11161 is a high-severity memory corruption vulnerability in Qualcomm Apq8053 Firmware, published on 9 Jun 2021. 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-11161 in the wild and no public exploit code.

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

## Sources

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

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