# CVE-2023-21628: Buffer Copy Without Checking Size of Input (`Classic Buffer Overflow`) in WLAN HAL

> A buffer overflow in Qualcomm Snapdragon WLAN HAL allows attackers to execute arbitrary code or escalate privileges via crafted WMI-UTF or FTM TLV1 commands.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 6 Jun 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-p6f2-8wjh-p66x

## What is CVE-2023-21628?

CVE-2023-21628 is a high-severity memory corruption vulnerability in Qualcomm Apq8017 Firmware, published on 6 Jun 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Memory corruption in WLAN HAL while processing WMI-UTF command or FTM TLV1 command.

Weakness: CWE-787 (Out-of-bounds Write), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2023-21628?

It affects 283 products.


Products: Qualcomm Apq8017 Firmware, Qualcomm Apq8064au Firmware, Qualcomm Apq8076 Firmware, Qualcomm Apq8092 Firmware, Qualcomm Apq8094 Firmware, Qualcomm Aqt1000 Firmware, Qualcomm Ar8031 Firmware, Qualcomm Ar8035 Firmware, Qualcomm Ar9380 Firmware, Qualcomm Csr8811 Firmware, Qualcomm Csra6620 Firmware, Qualcomm Csra6640 Firmware, Qualcomm Csrb31024 Firmware, Qualcomm Home Hub 100 Platform Firmware, Qualcomm Immersive Home 214 Platform Firmware, Qualcomm Immersive Home 216 Platform Firmware, Qualcomm Immersive Home 316 Platform Firmware, Qualcomm Immersive Home 318 Platform Firmware, Qualcomm Ipq4018 Firmware, Qualcomm Ipq4019 Firmware and 263 more.

## How do I fix CVE-2023-21628?

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

## Is CVE-2023-21628 being exploited?

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

## Other vulnerabilities in Qualcomm Apq8017 Firmware

- [CVE-2025-21483](https://insights.sbomify.com/CVE-2025-21483/): Improper Restriction of Operations within the Bounds of a Memory Buffer in Data Network Stack & Connectivity (critical 9.8)
- [CVE-2021-1933](https://insights.sbomify.com/CVE-2021-1933/): Denial of service in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Wearables (critical 9.8)
- [CVE-2021-1946](https://insights.sbomify.com/CVE-2021-1946/): Null dereference in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile (critical 9.8)
- [CVE-2020-11176](https://insights.sbomify.com/CVE-2020-11176/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile (critical 9.8)
- [CVE-2020-11291](https://insights.sbomify.com/CVE-2020-11291/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-21628 and fix it if it is affected.

What it is: CVE-2023-21628 is a high-severity memory corruption vulnerability in Qualcomm Apq8017 Firmware, published on 6 Jun 2023. 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-2023-21628 in the wild and no public exploit code.

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

## Sources

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

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