# CVE-2021-1928: Memory corruption in Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking

> A buffer over-read in Qualcomm Snapdragon firmware allows attackers to read sensitive memory or cause denial of service during eMMC flashing.

- **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:** No
- **Published:** 8 Sep 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-5cq3-xc35-2mw2

## What is CVE-2021-1928?

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

### Official description

Buffer over read could occur due to incorrect check of buffer size while flashing emmc devices in Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking

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

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

It affects 108 products.


Products: Qualcomm Apq8009 Firmware, Qualcomm Apq8053 Firmware, Qualcomm Ar9380 Firmware, Qualcomm Csr8811 Firmware, Qualcomm Ipq4018 Firmware, Qualcomm Ipq4019 Firmware, Qualcomm Ipq4028 Firmware, Qualcomm Ipq4029 Firmware, Qualcomm Ipq5010 Firmware, Qualcomm Ipq5018 Firmware, Qualcomm Ipq6000 Firmware, Qualcomm Ipq6005 Firmware, Qualcomm Ipq6010 Firmware, Qualcomm Ipq6018 Firmware, Qualcomm Ipq6028 Firmware, Qualcomm Ipq8064 Firmware, Qualcomm Ipq8065 Firmware, Qualcomm Ipq8068 Firmware, Qualcomm Ipq8069 Firmware, Qualcomm Ipq8070 Firmware and 88 more.

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

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

## Is CVE-2021-1928 being exploited?

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

## Other vulnerabilities in Qualcomm Apq8009 Firmware

- [CVE-2021-1905](https://insights.sbomify.com/CVE-2021-1905/): Qualcomm Multiple Chipsets Use-After-Free (high 8.4, exploited in the wild)
- [CVE-2020-11261](https://insights.sbomify.com/CVE-2020-11261/): Qualcomm Multiple Chipsets Improper Input Validation (high 7.8, exploited in the wild)
- [CVE-2021-1906](https://insights.sbomify.com/CVE-2021-1906/): Qualcomm Multiple Chipsets Detection of Error Condition Without Action (medium 6.2, exploited in the wild)
- [CVE-2022-40510](https://insights.sbomify.com/CVE-2022-40510/): Buffer copy without checking size of input in Audio. (critical 9.8)
- [CVE-2022-22088](https://insights.sbomify.com/CVE-2022-22088/): Integer Overflow to Buffer Overflow in Bluetooth HOST (critical 9.8)

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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