# CVE-2019-10569: Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Mobile

> A stack buffer overflow in Qualcomm Snapdragon firmware allows attackers to execute arbitrary code or escalate privileges via hardware accelerated effects.

- **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:** 5 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-rgf4-9xrf-jpv4

## What is CVE-2019-10569?

CVE-2019-10569 is a high-severity memory corruption vulnerability in Qualcomm Apq8053 Firmware, published on 5 Mar 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Stack buffer overflow due to instance id is misplaced inside definition of hardware accelerated effects in makefile in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Mobile in APQ8053, APQ8098, MDM9607, MDM9640, MSM8998, QCS605, SC8180X, SDM439, SDM630, SDM636, SDM660, SDM845, SDX24, SDX55, SM6150, SM7150, SM8150, SXR1130

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2019-10569?

It affects 18 products.


Products: Qualcomm Apq8053 Firmware, Qualcomm Apq8098 Firmware, Qualcomm Mdm9607 Firmware, Qualcomm Mdm9640 Firmware, Qualcomm Msm8998 Firmware, Qualcomm Qcs605 Firmware, Qualcomm Sc8180x Firmware, Qualcomm Sdm439 Firmware, Qualcomm Sdm630 Firmware, Qualcomm Sdm636 Firmware, Qualcomm Sdm660 Firmware, Qualcomm Sdm845 Firmware, Qualcomm Sdx24 Firmware, Qualcomm Sdx55 Firmware, Qualcomm Sm6150 Firmware, Qualcomm Sm7150 Firmware, Qualcomm Sm8150 Firmware, Qualcomm Sxr1130 Firmware.

## How do I fix CVE-2019-10569?

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

## Is CVE-2019-10569 being exploited?

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

## Other vulnerabilities in Qualcomm Apq8053 Firmware

- [CVE-2022-22071](https://insights.sbomify.com/CVE-2022-22071/): Qualcomm Multiple Chipsets Use-After-Free (high 8.4, exploited in the wild)
- [CVE-2020-11153](https://insights.sbomify.com/CVE-2020-11153/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile (critical 9.8)
- [CVE-2020-3703](https://insights.sbomify.com/CVE-2020-3703/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music (critical 9.8)
- [CVE-2019-14080](https://insights.sbomify.com/CVE-2019-14080/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables (critical 9.8)
- [CVE-2020-3628](https://insights.sbomify.com/CVE-2020-3628/): Information disclosure in Snapdragon Consumer IOT, Snapdragon Mobile (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-10569 and fix it if it is affected.

What it is: CVE-2019-10569 is a high-severity memory corruption vulnerability in Qualcomm Apq8053 Firmware, published on 5 Mar 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-2019-10569 in the wild and no public exploit code.

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

## Sources

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

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