# CVE-2020-11134: 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 stack out-of-bounds write in Snapdragon firmware allows attackers to execute arbitrary code or cause denial of service via malformed NAN management frames.

- **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:** No
- **Published:** 9 Jun 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-jmp3-rj28-rcjj

## What is CVE-2020-11134?

CVE-2020-11134 is a critical memory corruption vulnerability in Qualcomm Aqt1000 Firmware, published on 9 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Possible stack out of bound write might happen due to time bitmap length and bit duration fields of the attributes like NAN ranging setup attribute inside a NAN management frame are not Properly validated 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-787 (Out-of-bounds Write), CWE-129 (Improper Validation of Array Index)

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

It affects 325 products.


Products: Qualcomm Aqt1000 Firmware, Qualcomm Ar8031 Firmware, Qualcomm Ar8035 Firmware, Qualcomm Csr8811 Firmware, Qualcomm Csra6620 Firmware, Qualcomm Csra6640 Firmware, Qualcomm Ipq5010 Firmware, Qualcomm Ipq5018 Firmware, Qualcomm Ipq6000 Firmware, Qualcomm Ipq6005 Firmware, Qualcomm Ipq6010 Firmware, Qualcomm Ipq6018 Firmware, Qualcomm Ipq6028 Firmware, Qualcomm Ipq8070 Firmware, Qualcomm Ipq8070a Firmware, Qualcomm Ipq8071 Firmware, Qualcomm Ipq8071a Firmware, Qualcomm Ipq8072 Firmware, Qualcomm Ipq8072a Firmware, Qualcomm Ipq8074 Firmware and 305 more.

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

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

## Is CVE-2020-11134 being exploited?

There is no known exploitation of CVE-2020-11134 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-11134 and fix it if it is affected.

What it is: CVE-2020-11134 is a critical memory corruption vulnerability in Qualcomm Aqt1000 Firmware, published on 9 Jun 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-11134 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-11134/ (Markdown: https://insights.sbomify.com/CVE-2020-11134/index.md)
```

## Sources

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

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