# CVE-2020-3699: Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables

> Out-of-bounds write in Snapdragon firmware allows attackers to execute arbitrary code or escalate privileges via malicious association responses.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Jul 2020
- **Updated:** 4 Aug 2024
- **Also known as:** 2583124, 2616229, A-153344687, ASB-A-153344687, GHSA-9rj4-m4p5-2v9x

## What is CVE-2020-3699?

CVE-2020-3699 is a critical memory corruption vulnerability in Qualcomm Apq8009 Firmware, published on 30 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Possible out of bound access while processing assoc response from host due to improper length check before copying into buffer in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in APQ8009, APQ8017, APQ8053, APQ8096AU, MDM9206, MDM9207C, MDM9607, MDM9640, MDM9650, MSM8905, MSM8909W, MSM8917, MSM8920, MSM8937, MSM8940, MSM8953, MSM8996AU, Nicobar, QCA6174A, QCA6574AU, QCA9377, QCA9379, QCM2150, QCN7605, QCS405, QCS605, QM215, SA6155P, Saipan, SC8180X, SDA845, SDM429, SDM429W, SDM439, SDM450, SDM630, SDM632, SDM636, SDM660, SDM845, SDX20, SDX55, SM6150, SM7150, SM8150, SM8250, SXR2130

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

## Which versions are affected by CVE-2020-3699?

It affects 47 products.


Products: Qualcomm Apq8009 Firmware, Qualcomm Apq8017 Firmware, Qualcomm Apq8053 Firmware, Qualcomm Apq8096au Firmware, Qualcomm Mdm9206 Firmware, Qualcomm Mdm9207c Firmware, Qualcomm Mdm9607 Firmware, Qualcomm Mdm9640 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Msm8905 Firmware, Qualcomm Msm8909w Firmware, Qualcomm Msm8917 Firmware, Qualcomm Msm8920 Firmware, Qualcomm Msm8937 Firmware, Qualcomm Msm8940 Firmware, Qualcomm Msm8953 Firmware, Qualcomm Msm8996au Firmware, Qualcomm Nicobar Firmware, Qualcomm Qca6174a Firmware, Qualcomm Qca6574au Firmware and 27 more.

## How do I fix CVE-2020-3699?

Apply the vendor's patch.

## Is CVE-2020-3699 being exploited?

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

What it is: CVE-2020-3699 is a critical memory corruption vulnerability in Qualcomm Apq8009 Firmware, published on 30 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-3699 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-2020-3699/ (Markdown: https://insights.sbomify.com/CVE-2020-3699/index.md)
```

## Sources

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

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