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

> Improper validation of EFS file write size allows memory corruption, potentially enabling code execution or privilege escalation on Snapdragon devices.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 11 Feb 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-33mh-74gh-7rp5

## What is CVE-2021-30323?

CVE-2021-30323 is a high-severity memory corruption vulnerability in Qualcomm Apq8009w Firmware, published on 11 Feb 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper validation of maximum size of data write to EFS file can lead to memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables

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

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

It affects 101 products.


Products: Qualcomm Apq8009w Firmware, Qualcomm Apq8017 Firmware, Qualcomm Apq8053 Firmware, Qualcomm Apq8096au Firmware, Qualcomm Aqt1000 Firmware, Qualcomm Csrb31024 Firmware, Qualcomm Mdm8207 Firmware, Qualcomm Mdm9150 Firmware, Qualcomm Mdm9205 Firmware, Qualcomm Mdm9206 Firmware, Qualcomm Mdm9207 Firmware, Qualcomm Mdm9250 Firmware, Qualcomm Mdm9607 Firmware, Qualcomm Mdm9628 Firmware, Qualcomm Mdm9640 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Mdm9655 Firmware, Qualcomm Msm8909w Firmware, Qualcomm Msm8953 Firmware, Qualcomm Msm8996au Firmware and 81 more.

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

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

## Is CVE-2021-30323 being exploited?

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

## Other vulnerabilities in Qualcomm Apq8009w Firmware

- [CVE-2021-30341](https://insights.sbomify.com/CVE-2021-30341/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Wearables (critical 9.8)
- [CVE-2021-35104](https://insights.sbomify.com/CVE-2021-35104/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking (critical 9.8)
- [CVE-2020-11307](https://insights.sbomify.com/CVE-2020-11307/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Wearables (critical 9.8)
- [CVE-2021-30342](https://insights.sbomify.com/CVE-2021-30342/): Race condition in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.1)
- [CVE-2021-30334](https://insights.sbomify.com/CVE-2021-30334/): Use after free in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music, Snapdragon Wearables (high 8.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-30323 is a high-severity memory corruption vulnerability in Qualcomm Apq8009w Firmware, published on 11 Feb 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-30323 in the wild and no public exploit code.

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

## Sources

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

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