# CVE-2020-11187: Memory corruption in Snapdragon Auto, Snapdragon Connectivity, Snapdragon Mobile

> Attackers can exploit improper parameter validation in the BSI module to cause memory corruption, potentially leading to code execution or privilege escalation 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:** 22 Feb 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2xq2-3g36-329g

## What is CVE-2020-11187?

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

### Official description

Possible memory corruption in BSI module due to improper validation of parameter count in Snapdragon Auto, Snapdragon Connectivity, Snapdragon Mobile

Weakness: CWE-129 (Improper Validation of Array Index)

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

It affects 98 products.


Products: Qualcomm Aqt1000 Firmware, Qualcomm Csrb31024 Firmware, Qualcomm Pm7150a Firmware, Qualcomm Pm7150l Firmware, Qualcomm Pm7250 Firmware, Qualcomm Pm7250b Firmware, Qualcomm Pm8004 Firmware, Qualcomm Pm8008 Firmware, Qualcomm Pm855 Firmware, Qualcomm Pm855b Firmware, Qualcomm Pm855l Firmware, Qualcomm Pm855p Firmware, Qualcomm Pmk8002 Firmware, Qualcomm Pmx24 Firmware, Qualcomm Pmx50 Firmware, Qualcomm Pmx55 Firmware, Qualcomm Qat3516 Firmware, Qualcomm Qat3518 Firmware, Qualcomm Qat3519 Firmware, Qualcomm Qat3555 Firmware and 78 more.

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

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

## Is CVE-2020-11187 being exploited?

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

## Other vulnerabilities in Qualcomm Aqt1000 Firmware

- [CVE-2025-21479](https://insights.sbomify.com/CVE-2025-21479/): Qualcomm Multiple Chipsets Incorrect Authorization (high 8.6, exploited in the wild)
- [CVE-2025-21480](https://insights.sbomify.com/CVE-2025-21480/): Qualcomm Multiple Chipsets Incorrect Authorization (high 8.6, exploited in the wild)
- [CVE-2023-28562](https://insights.sbomify.com/CVE-2023-28562/): Buffer Copy Without Checking Size of Input in QESL (critical 9.8)
- [CVE-2022-40514](https://insights.sbomify.com/CVE-2022-40514/): Buffer copy without checking size of input in WLAN Firmware (critical 9.8)
- [CVE-2022-22096](https://insights.sbomify.com/CVE-2022-22096/): Memory corruption in Snapdragon Connectivity, Snapdragon Mobile (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-11187 is a high-severity memory corruption vulnerability in Qualcomm Aqt1000 Firmware, published on 22 Feb 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-11187 in the wild and no public exploit code.

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

## Sources

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

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