# CVE-2021-30331: Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables

> A buffer overflow in the DIAG interface allows attackers to execute arbitrary code or escalate privileges on Qualcomm Snapdragon devices.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Apr 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-cjmw-x525-6p4f

## What is CVE-2021-30331?

CVE-2021-30331 is a medium-severity memory corruption vulnerability in Qualcomm Ar8035 Firmware, published on 1 Apr 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Possible buffer overflow due to improper data validation of external commands sent via DIAG interface in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 77 products.


Products: Qualcomm Ar8035 Firmware, Qualcomm Fsm10055 Firmware, Qualcomm Fsm10056 Firmware, Qualcomm Mdm9150 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Qca6174a Firmware, Qualcomm Qca6390 Firmware, Qualcomm Qca6391 Firmware, Qualcomm Qca6426 Firmware, Qualcomm Qca6436 Firmware, Qualcomm Qca8081 Firmware, Qualcomm Qca8337 Firmware, Qualcomm Qca9377 Firmware, Qualcomm Qcm2290 Firmware, Qualcomm Qcm4290 Firmware, Qualcomm Qcm6125 Firmware, Qualcomm Qcm6490 Firmware, Qualcomm Qcs2290 Firmware, Qualcomm Qcs410 Firmware, Qualcomm Qcs4290 Firmware and 57 more.

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

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

## Is CVE-2021-30331 being exploited?

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

## Other vulnerabilities in Qualcomm Ar8035 Firmware

- [CVE-2023-33106](https://insights.sbomify.com/CVE-2023-33106/): Qualcomm Multiple Chipsets Use of Out-of-Range Pointer Offset (high 8.4, exploited in the wild)
- [CVE-2024-45569](https://insights.sbomify.com/CVE-2024-45569/): Improper Validation of Array Index in WLAN Host Communication (critical 9.8)
- [CVE-2024-21473](https://insights.sbomify.com/CVE-2024-21473/): Improper Input Validation in WIN SON (critical 9.8)
- [CVE-2023-28582](https://insights.sbomify.com/CVE-2023-28582/): Buffer Copy Without Checking Size of Input in Data Modem (critical 9.8)
- [CVE-2023-43552](https://insights.sbomify.com/CVE-2023-43552/): Use After Free in WLAN Host Communication (critical 9.8)

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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