# CVE-2021-35117: Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music

> Out-of-bounds read in Qualcomm Snapdragon firmware allows attackers to cause denial of service or disclose information via crafted IBSS beacons.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Apr 2022
- **Updated:** 4 Aug 2024
- **Also known as:** 3028360, A-209481202, ASB-A-209481202, GHSA-83q3-7jfp-3xww

## What is CVE-2021-35117?

CVE-2021-35117 is a high-severity memory corruption vulnerability in Qualcomm Apq8096au Firmware, published on 1 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An Out of Bounds read may potentially occur while processing an IBSS beacon, in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music

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

## Which versions are affected by CVE-2021-35117?

It affects 102 products.


Products: Qualcomm Apq8096au Firmware, Qualcomm Aqt1000 Firmware, Qualcomm Ar8031 Firmware, Qualcomm Ar8035 Firmware, Qualcomm Csra6620 Firmware, Qualcomm Csra6640 Firmware, Qualcomm Csrb31024 Firmware, Qualcomm Msm8996au Firmware, Qualcomm Qca6175a Firmware, Qualcomm Qca6390 Firmware, Qualcomm Qca6391 Firmware, Qualcomm Qca6426 Firmware, Qualcomm Qca6436 Firmware, Qualcomm Qca6554a Firmware, Qualcomm Qca6564 Firmware, Qualcomm Qca6564a Firmware, Qualcomm Qca6564au Firmware, Qualcomm Qca6574 Firmware, Qualcomm Qca6574a Firmware, Qualcomm Qca6574au Firmware and 82 more.

## How do I fix CVE-2021-35117?

Apply the vendor's patch.

## Is CVE-2021-35117 being exploited?

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

## Other vulnerabilities in Qualcomm Apq8096au Firmware

- [CVE-2019-14045](https://insights.sbomify.com/CVE-2019-14045/): Memory corruption in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Mobile (critical 9.8)
- [CVE-2017-14911](https://insights.sbomify.com/CVE-2017-14911/): Auth bypass in Snapdragon IoT, Snapdragon Mobile, Snapdragon Automobile (critical 9.8)
- [CVE-2020-11126](https://insights.sbomify.com/CVE-2020-11126/): 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-2022-33243](https://insights.sbomify.com/CVE-2022-33243/): Improper access control in Qualcomm IPC (high 8.4)
- [CVE-2022-22063](https://insights.sbomify.com/CVE-2022-22063/): Memory corruption in Core (high 8.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-35117 and fix it if it is affected.

What it is: CVE-2021-35117 is a high-severity memory corruption vulnerability in Qualcomm Apq8096au Firmware, published on 1 Apr 2022. 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-2021-35117 in the wild and no public exploit code.

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

## Sources

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

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