# CVE-2020-11264: Auth bypass in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music

> Improper authentication in the four-way handshake allows attackers to inject arbitrary network packets into Snapdragon-based devices.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Sep 2021
- **Updated:** 4 Aug 2024
- **Also known as:** 2860206, A-175608649, ASB-A-175608649, GHSA-jm3v-7p2w-cvmp

## What is CVE-2020-11264?

CVE-2020-11264 is a critical authentication bypass vulnerability in Qualcomm Apq8053 Firmware, published on 8 Sep 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper authentication of Non-EAPOL/WAPI plaintext frames during four-way handshake can lead to arbitrary network packet injection in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music

Weakness: CWE-287 (Improper Authentication)

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

It affects 126 products.


Products: Qualcomm Apq8053 Firmware, Qualcomm Apq8064au Firmware, Qualcomm Apq8096au Firmware, Qualcomm Aqt1000 Firmware, Qualcomm Ar8031 Firmware, Qualcomm Ar8035 Firmware, Qualcomm Csra6620 Firmware, Qualcomm Csra6640 Firmware, Qualcomm Csrb31024 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Msm8953 Firmware, Qualcomm Msm8996au Firmware, Qualcomm Qca1062 Firmware, Qualcomm Qca1064 Firmware, Qualcomm Qca2062 Firmware, Qualcomm Qca2064 Firmware, Qualcomm Qca2065 Firmware, Qualcomm Qca2066 Firmware, Qualcomm Qca6164 Firmware, Qualcomm Qca6174 Firmware and 106 more.

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

Apply the vendor's patch.

## Is CVE-2020-11264 being exploited?

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

## Other vulnerabilities in Qualcomm Apq8053 Firmware

- [CVE-2022-22071](https://insights.sbomify.com/CVE-2022-22071/): Qualcomm Multiple Chipsets Use-After-Free (high 8.4, exploited in the wild)
- [CVE-2020-11153](https://insights.sbomify.com/CVE-2020-11153/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile (critical 9.8)
- [CVE-2020-3703](https://insights.sbomify.com/CVE-2020-3703/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music (critical 9.8)
- [CVE-2019-14080](https://insights.sbomify.com/CVE-2019-14080/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables (critical 9.8)
- [CVE-2020-3628](https://insights.sbomify.com/CVE-2020-3628/): Information disclosure in Snapdragon Consumer IOT, Snapdragon Mobile (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-11264 is a critical authentication bypass vulnerability in Qualcomm Apq8053 Firmware, published on 8 Sep 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-11264 in the wild and no public exploit code.

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

## Sources

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

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