# CVE-2021-1899: Memory corruption in Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables

> A buffer over-read in Qualcomm Snapdragon firmware allows attackers to potentially execute code or cause denial of service via crafted meta images.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:P/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Jul 2021
- **Updated:** 3 Aug 2024
- **Also known as:** 2776412, A-176750676, GHSA-cm5j-mgw2-2jwr, PUB-A-176750676

## What is CVE-2021-1899?

CVE-2021-1899 is a medium-severity memory corruption vulnerability in Qualcomm Apq8009w Firmware, published on 13 Jul 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Possible buffer over read due to lack of length check while flashing meta images in Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables

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

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

It affects 41 products.


Products: Qualcomm Apq8009w Firmware, Qualcomm Aqt1000 Firmware, Qualcomm Msm8909w Firmware, Qualcomm Qca4020 Firmware, Qualcomm Qca6174a Firmware, Qualcomm Qca6420 Firmware, Qualcomm Qca6430 Firmware, Qualcomm Qca9379 Firmware, Qualcomm Qualcomm215 Firmware, Qualcomm Sd205 Firmware, Qualcomm Sd210 Firmware, Qualcomm Sd675 Firmware, Qualcomm Sd678 Firmware, Qualcomm Sd720g Firmware, Qualcomm Sd730 Firmware, Qualcomm Sd855 Firmware, Qualcomm Sd 675 Firmware, Qualcomm Sda429w Firmware, Qualcomm Sdm429w Firmware, Qualcomm Sdx50m Firmware and 21 more.

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

Apply the vendor's patch.

## Is CVE-2021-1899 being exploited?

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

What it is: CVE-2021-1899 is a medium-severity memory corruption vulnerability in Qualcomm Apq8009w Firmware, published on 13 Jul 2021. 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-1899 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-1899/ (Markdown: https://insights.sbomify.com/CVE-2021-1899/index.md)
```

## Sources

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

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