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

> Out-of-bounds access in MHI command processing 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:** Yes
- **Published:** 9 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** 2580967, A-157905780, ASB-A-157905780, GHSA-j657-99m2-wp3h

## What is CVE-2020-3656?

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

### Official description

Out of bound access can happen in MHI command process due to lack of check of command channel id value received from MHI devices in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in APQ8009, Kamorta, MDM9607, MSM8917, MSM8953, Nicobar, QCM2150, QCS405, QCS605, QM215, Rennell, SA6155P, SA8155P, Saipan, SC8180X, SDM429, SDM429W, SDM439, SDM450, SDM632, SDM710, SDM845, SDX55, SM6150, SM7150, SM8150, SM8250, SXR2130

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

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

It affects 28 products.


Products: Qualcomm Apq8009 Firmware, Qualcomm Kamorta Firmware, Qualcomm Mdm9607 Firmware, Qualcomm Msm8917 Firmware, Qualcomm Msm8953 Firmware, Qualcomm Nicobar Firmware, Qualcomm Qcm2150 Firmware, Qualcomm Qcs405 Firmware, Qualcomm Qcs605 Firmware, Qualcomm Qm215 Firmware, Qualcomm Rennell Firmware, Qualcomm Sa6155p Firmware, Qualcomm Sa8155p Firmware, Qualcomm Saipan Firmware, Qualcomm Sc8180x Firmware, Qualcomm Sdm429 Firmware, Qualcomm Sdm429w Firmware, Qualcomm Sdm439 Firmware, Qualcomm Sdm450 Firmware, Qualcomm Sdm632 Firmware and 8 more.

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

Apply the vendor's patch.

## Is CVE-2020-3656 being exploited?

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

What it is: CVE-2020-3656 is a high-severity memory corruption vulnerability in Qualcomm Apq8009 Firmware, published on 9 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-3656 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-3656/ (Markdown: https://insights.sbomify.com/CVE-2020-3656/index.md)
```

## Sources

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

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