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

> Remote attackers can trigger memory corruption in Bluetooth L2CAP reassembly logic, potentially leading to code execution or privilege escalation on Snapdragon devices.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Jan 2021
- **Updated:** 4 Aug 2024
- **Also known as:** 2434229, A-168049959, ASB-A-168049959, GHSA-792j-8wv9-hgmh

## What is CVE-2020-11167?

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

### Official description

Memory corruption while calculating L2CAP packet length in reassembly logic when remote sends more data than expected in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables

Weakness: CWE-787 (Out-of-bounds Write), CWE-190 (Integer Overflow or Wraparound)

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

It affects 286 products.


Products: Qualcomm Apq8009w, Qualcomm Apq8017, Qualcomm Apq8037, Qualcomm Apq8053, Qualcomm Apq8064au, Qualcomm Apq8096au, Qualcomm Aqt1000, Qualcomm Msm8909w, Qualcomm Msm8917, Qualcomm Msm8920, Qualcomm Msm8937, Qualcomm Msm8940, Qualcomm Msm8953, Qualcomm Msm8996au, Qualcomm Pm215, Qualcomm Pm3003a, Qualcomm Pm439, Qualcomm Pm6125, Qualcomm Pm6150, Qualcomm Pm6150a and 266 more.

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

Apply the vendor's patch.

## Is CVE-2020-11167 being exploited?

There is no known exploitation of CVE-2020-11167 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-11152](https://insights.sbomify.com/CVE-2020-11152/): Race condition in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (medium 6.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-11167 is a critical 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. 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-11167 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-11167/ (Markdown: https://insights.sbomify.com/CVE-2020-11167/index.md)
```

## Sources

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

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