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

> A buffer over-read in Qualcomm Snapdragon firmware allows attackers to cause denial of service or disclose sensitive information via malformed RPS input.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jan 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-j5cw-ghxr-f273

## What is CVE-2020-11200?

CVE-2020-11200 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. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer over-read while parsing RPS due to lack of check of input validation on values received from user side. in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile

Weakness: CWE-20 (Improper Input Validation), CWE-125 (Out-of-bounds Read)

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

It affects 330 products.


Products: Qualcomm Apq8053, Qualcomm Apq8064au, Qualcomm Apq8096au, Qualcomm Aqt1000, Qualcomm Ar8151, Qualcomm Mdm9640, Qualcomm Mdm9650, Qualcomm Msm8953, Qualcomm Msm8996au, Qualcomm Pm3003a, Qualcomm Pm4125, Qualcomm Pm456, Qualcomm Pm6125, Qualcomm Pm6150, Qualcomm Pm6150a, Qualcomm Pm6150l, Qualcomm Pm6250, Qualcomm Pm6350, Qualcomm Pm640a, Qualcomm Pm640l and 310 more.

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

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

## Is CVE-2020-11200 being exploited?

There is no known exploitation of CVE-2020-11200 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-11149](https://insights.sbomify.com/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 (medium 6.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-11200 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. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-11200 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-11200/ (Markdown: https://insights.sbomify.com/CVE-2020-11200/index.md)
```

## Sources

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

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