# CVE-2021-35113: Auth bypass in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables

> Attackers can bypass authentication in Qualcomm Snapdragon firmware due to improper signature verification order, affecting multiple device categories.

- **Severity:** High 7.3 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Sep 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-73v4-jjr8-v4cq

## What is CVE-2021-35113?

CVE-2021-35113 is a high-severity authentication bypass vulnerability in Qualcomm Aqt1000 Firmware, published on 2 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Possible authentication bypass due to improper order of signature verification and hashing in the signature verification call in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

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

It affects 48 products.


Products: Qualcomm Aqt1000 Firmware, Qualcomm Csrb31024 Firmware, Qualcomm Qca6174a Firmware, Qualcomm Qca6310 Firmware, Qualcomm Qca6335 Firmware, Qualcomm Qca6420 Firmware, Qualcomm Qca6430 Firmware, Qualcomm Qca6564au Firmware, Qualcomm Qca6574au Firmware, Qualcomm Qca6595au Firmware, Qualcomm Qca6696 Firmware, Qualcomm Qca9377 Firmware, Qualcomm Qcs410 Firmware, Qualcomm Qcs610 Firmware, Qualcomm Sa415m Firmware, Qualcomm Sd429 Firmware, Qualcomm Sd675 Firmware, Qualcomm Sd678 Firmware, Qualcomm Sd720g Firmware, Qualcomm Sd730 Firmware and 28 more.

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

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

## Is CVE-2021-35113 being exploited?

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

What it is: CVE-2021-35113 is a high-severity authentication bypass vulnerability in Qualcomm Aqt1000 Firmware, published on 2 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-35113 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-2021-35113/ (Markdown: https://insights.sbomify.com/CVE-2021-35113/index.md)
```

## Sources

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

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