# CVE-2020-11180: Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile

> Out-of-bounds access in computer vision control allows attackers to execute arbitrary code or cause denial of service on 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:** 21 Jan 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-cg67-rx3c-vx3q

## What is CVE-2020-11180?

CVE-2020-11180 is a high-severity memory corruption vulnerability in Qualcomm, Inc. Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, published on 21 Jan 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Out of bound access in computer vision control due to improper validation of command length before processing it in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 158 products.


Products: Qualcomm Aqt1000, Qualcomm Pm3003a, Qualcomm Pm6150, Qualcomm Pm7150a, Qualcomm Pm7150l, Qualcomm Pm7250, Qualcomm Pm7250b, Qualcomm Pm8004, Qualcomm Pm8008, Qualcomm Pm8009, Qualcomm Pm8150, Qualcomm Pm8150a, Qualcomm Pm8150b, Qualcomm Pm8150c, Qualcomm Pm8150l, Qualcomm Pm8250, Qualcomm Pm855, Qualcomm Pm855b, Qualcomm Pm855l, Qualcomm Pm855p and 138 more.

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

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

## Is CVE-2020-11180 being exploited?

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

## Other vulnerabilities in Qualcomm, Inc. Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile

- [CVE-2020-11215](https://insights.sbomify.com/CVE-2020-11215/): 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.1)
- [CVE-2020-11287](https://insights.sbomify.com/CVE-2020-11287/): Information disclosure 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 (high 7.5)
- [CVE-2020-11214](https://insights.sbomify.com/CVE-2020-11214/): 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 (high 7.5)
- [CVE-2020-11150](https://insights.sbomify.com/CVE-2020-11150/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (medium 6.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-11180 is a high-severity memory corruption vulnerability in Qualcomm, Inc. Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, published on 21 Jan 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-11180 in the wild and no public exploit code.

Affected product: Qualcomm, Inc. Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile. 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-11180/ (Markdown: https://insights.sbomify.com/CVE-2020-11180/index.md)
```

## Sources

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

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