# CVE-2020-11154: 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

> A buffer overflow in Qualcomm Snapdragon Bluetooth firmware allows attackers to execute arbitrary code or cause denial of service via crafted packets.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9m5h-pgq6-39gc

## What is CVE-2020-11154?

CVE-2020-11154 is a high-severity memory corruption vulnerability in Qualcomm Apq8009 Firmware, published on 2 Nov 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

u'Buffer overflow while processing a crafted PDU data packet in bluetooth due to lack of check of buffer size before copying' 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 in APQ8009, APQ8053, QCA6390, QCN7605, QCN7606, SA415M, SA515M, SA6155P, SA8155P, SC8180X, SDX55

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 11 products.


Products: Qualcomm Apq8009 Firmware, Qualcomm Apq8053 Firmware, Qualcomm Qca6390 Firmware, Qualcomm Qcn7605 Firmware, Qualcomm Qcn7606 Firmware, Qualcomm Sa415m Firmware, Qualcomm Sa515m Firmware, Qualcomm Sa6155p Firmware, Qualcomm Sa8155p Firmware, Qualcomm Sc8180x Firmware, Qualcomm Sdx55 Firmware.

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

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

## Is CVE-2020-11154 being exploited?

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

## Other vulnerabilities in Qualcomm Apq8009 Firmware

- [CVE-2021-1905](https://insights.sbomify.com/CVE-2021-1905/): Qualcomm Multiple Chipsets Use-After-Free (high 8.4, exploited in the wild)
- [CVE-2020-11261](https://insights.sbomify.com/CVE-2020-11261/): Qualcomm Multiple Chipsets Improper Input Validation (high 7.8, exploited in the wild)
- [CVE-2021-1906](https://insights.sbomify.com/CVE-2021-1906/): Qualcomm Multiple Chipsets Detection of Error Condition Without Action (medium 6.2, exploited in the wild)
- [CVE-2022-40510](https://insights.sbomify.com/CVE-2022-40510/): Buffer copy without checking size of input in Audio. (critical 9.8)
- [CVE-2022-22088](https://insights.sbomify.com/CVE-2022-22088/): Integer Overflow to Buffer Overflow in Bluetooth HOST (critical 9.8)

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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