# CVE-2020-11287: Information disclosure 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

> An attacker can disclose information by linking RTT frames with non-randomized MAC addresses via sequence number comparison in Qualcomm Snapdragon chipsets.

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

## What is CVE-2020-11287?

CVE-2020-11287 is a high-severity vulnerability in Qualcomm, Inc. 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, published on 22 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Allowing RTT frames to be linked with non randomized MAC address by comparing the sequence numbers can lead to information disclosure. 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

Weakness: CWE-203 (Observable Discrepancy)

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

It affects 329 products.


Products: Qualcomm Aqt1000, Qualcomm Ar8031, Qualcomm Ar8035, Qualcomm Csr8811, Qualcomm Csra6620, Qualcomm Csra6640, Qualcomm Csrb31024, Qualcomm Ipq6000, Qualcomm Ipq6010, Qualcomm Ipq6018, Qualcomm Ipq6028, Qualcomm Ipq8070, Qualcomm Ipq8070a, Qualcomm Ipq8071, Qualcomm Ipq8071a, Qualcomm Ipq8072, Qualcomm Ipq8072a, Qualcomm Ipq8074, Qualcomm Ipq8074a, Qualcomm Ipq8076 and 309 more.

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

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

## Is CVE-2020-11287 being exploited?

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

## Other vulnerabilities in Qualcomm, Inc. 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

- [CVE-2020-11215](https://insights.sbomify.com/CVE-2020-11215/): 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 (critical 9.1)
- [CVE-2020-11180](https://insights.sbomify.com/CVE-2020-11180/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile (high 7.8)
- [CVE-2020-11214](https://insights.sbomify.com/CVE-2020-11214/): 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 (high 7.5)
- [CVE-2020-11150](https://insights.sbomify.com/CVE-2020-11150/): 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-11287 and fix it if it is affected.

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

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

## Sources

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

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