# CVE-2020-3646: Memory corruption in Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables

> A buffer overflow in the video application allows attackers to execute arbitrary code or escalate privileges on affected Qualcomm 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:** 8 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-m69w-8p53-w8cx

## What is CVE-2020-3646?

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

### Official description

u'Buffer overflow seen as the destination buffer size is lesser than the source buffer size in video application' in Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in Bitra, MSM8909W, QCM2150, QCS405, QCS605, Saipan, SC8180X, SDA845, SDM429W, SDX24, SDX55, SM6150, SM7150, SM8150, SM8250, SXR2130

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

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

It affects 16 products.


Products: Qualcomm Bitra Firmware, Qualcomm Msm8909w Firmware, Qualcomm Qcm2150 Firmware, Qualcomm Qcs405 Firmware, Qualcomm Qcs605 Firmware, Qualcomm Saipan Firmware, Qualcomm Sc8180x Firmware, Qualcomm Sda845 Firmware, Qualcomm Sdm429w Firmware, Qualcomm Sdx24 Firmware, Qualcomm Sdx55 Firmware, Qualcomm Sm6150 Firmware, Qualcomm Sm7150 Firmware, Qualcomm Sm8150 Firmware, Qualcomm Sm8250 Firmware, Qualcomm Sxr2130 Firmware.

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

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

## Is CVE-2020-3646 being exploited?

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

## Other vulnerabilities in Qualcomm Msm8909w Firmware

- [CVE-2020-3694](https://insights.sbomify.com/CVE-2020-3694/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Mobile, Snapdragon Voice & Music (high 7.8)
- [CVE-2020-11129](https://insights.sbomify.com/CVE-2020-11129/): Use after free in Snapdragon Consumer IOT, Snapdragon Mobile (high 7.8)
- [CVE-2019-10596](https://insights.sbomify.com/CVE-2019-10596/): Missing authorization in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking (high 7.8)
- [CVE-2019-10629](https://insights.sbomify.com/CVE-2019-10629/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking (high 7.8)
- [CVE-2019-13992](https://insights.sbomify.com/CVE-2019-13992/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-3646 and fix it if it is affected.

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

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

## Sources

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

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