# CVE-2020-3625: Memory corruption in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Mobile

> A stack out-of-bounds write in Qualcomm Snapdragon DSP capabilities query allows attackers to execute arbitrary code or cause denial of service.

- **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:** 2 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-7x9v-q273-743q

## What is CVE-2020-3625?

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

### Official description

When making query to DSP capabilities, Stack out of bounds occurs due to wrong buffer length configured for DSP attributes in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Mobile in SM8250, SXR2130

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

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

It affects 2 products.


Products: Qualcomm Sm8250 Firmware, Qualcomm Sxr2130 Firmware.

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

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

## Is CVE-2020-3625 being exploited?

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

## Other vulnerabilities in Qualcomm Sm8250 Firmware

- [CVE-2020-3623](https://insights.sbomify.com/CVE-2020-3623/): Denial of service in Snapdragon Mobile (high 7.8)

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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