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

> Out-of-bounds access in the camera driver allows attackers to execute arbitrary code or escalate privileges on Snapdragon devices.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **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-mpxx-6gg7-w2hx

## What is CVE-2020-11149?

CVE-2020-11149 is a medium-severity memory corruption vulnerability in Qualcomm, Inc. Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, 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 due to usage of an out-of-range pointer offset in the camera driver. in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables

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

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

It affects 293 products.


Products: Qualcomm Apq8053, Qualcomm Apq8096au, Qualcomm Aqt1000, Qualcomm Ar8031, Qualcomm Ar8035, Qualcomm Csra6620, Qualcomm Csra6640, Qualcomm Mdm9650, Qualcomm Pm215, Qualcomm Pm3003a, Qualcomm Pm6125, Qualcomm Pm6150, Qualcomm Pm6150a, Qualcomm Pm6150l, Qualcomm Pm6350, Qualcomm Pm640a, Qualcomm Pm640l, Qualcomm Pm640p, Qualcomm Pm660, Qualcomm Pm660l and 273 more.

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

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

## Is CVE-2020-11149 being exploited?

There is no known exploitation of CVE-2020-11149 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, Snapdragon Voice & Music, Snapdragon Wearables

- [CVE-2020-11200](https://insights.sbomify.com/CVE-2020-11200/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-11149 is a medium-severity memory corruption vulnerability in Qualcomm, Inc. Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, 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-11149 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, Snapdragon Voice & Music, Snapdragon Wearables. 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-11149/ (Markdown: https://insights.sbomify.com/CVE-2020-11149/index.md)
```

## Sources

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

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