# CVE-2020-11241: 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, Snapdragon Wired Infrastructure and Networking

> An out-of-bounds read in Qualcomm Snapdragon firmware allows attackers to cause denial of service or disclose sensitive information via malformed EAPOL Key lengths.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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-fhqp-v95c-jh5f

## What is CVE-2020-11241?

CVE-2020-11241 is a high-severity memory corruption vulnerability in Qualcomm Apq8009 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

Out of bound read will happen if EAPOL Key length is less than expected while processing NAN shared key descriptor attribute in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 426 products.


Products: Qualcomm Apq8009 Firmware, Qualcomm Apq8096au Firmware, Qualcomm Aqt1000 Firmware, Qualcomm Ar8031 Firmware, Qualcomm Ar8035 Firmware, Qualcomm Ar9380 Firmware, Qualcomm Csr8811 Firmware, Qualcomm Csra6620 Firmware, Qualcomm Csra6640 Firmware, Qualcomm Csrb31024 Firmware, Qualcomm Ipq4018 Firmware, Qualcomm Ipq4028 Firmware, Qualcomm Ipq4029 Firmware, Qualcomm Ipq5010 Firmware, Qualcomm Ipq5018 Firmware, Qualcomm Ipq6000 Firmware, Qualcomm Ipq6005 Firmware, Qualcomm Ipq6010 Firmware, Qualcomm Ipq6018 Firmware, Qualcomm Ipq6028 Firmware and 406 more.

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

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

## Is CVE-2020-11241 being exploited?

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

What it is: CVE-2020-11241 is a high-severity memory corruption vulnerability in Qualcomm Apq8009 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-11241 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-11241/ (Markdown: https://insights.sbomify.com/CVE-2020-11241/index.md)
```

## Sources

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

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