# CVE-2019-2256: Code injection in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables

> An unprivileged user can achieve code execution by crafting a malicious bitstream, affecting various Qualcomm Snapdragon platforms.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** No
- **Published:** 14 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-mfrv-fwwq-96p5

## What is CVE-2019-2256?

CVE-2019-2256 is a critical code injection vulnerability in Qualcomm Mdm9650 Firmware, published on 14 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An unprivileged user can craft a bitstream such that the payload encoded in the bitstream gains code execution in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in MDM9650, MSM8909W, MSM8996AU, QCS605, Qualcomm 215, SD 210/SD 212/SD 205, SD 425, SD 427, SD 430, SD 435, SD 439 / SD 429, SD 450, SD 625, SD 632, SD 636, SD 675, SD 712 / SD 710 / SD 670, SD 820, SD 820A, SD 835, SD 845 / SD 850, SD 855, SD 8CX, SDA660, SDM439, SDM630, SDM660, Snapdragon_High_Med_2016, SXR1130

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

It affects 35 products.


Products: Qualcomm Mdm9650 Firmware, Qualcomm Msm8909w Firmware, Qualcomm Msm8996au Firmware, Qualcomm Qcs605 Firmware, Qualcomm Qm215 Firmware, Qualcomm Sd 205 Firmware, Qualcomm Sd 210 Firmware, Qualcomm Sd 212 Firmware, Qualcomm Sd 425 Firmware, Qualcomm Sd 427 Firmware, Qualcomm Sd 429 Firmware, Qualcomm Sd 430 Firmware, Qualcomm Sd 435 Firmware, Qualcomm Sd 439 Firmware, Qualcomm Sd 450 Firmware, Qualcomm Sd 625 Firmware, Qualcomm Sd 632 Firmware, Qualcomm Sd 636 Firmware, Qualcomm Sd 670 Firmware, Qualcomm Sd 675 Firmware and 15 more.

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

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

## Is CVE-2019-2256 being exploited?

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

## Other vulnerabilities in Qualcomm Mdm9650 Firmware

- [CVE-2019-2252](https://insights.sbomify.com/CVE-2019-2252/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)
- [CVE-2016-10461](https://insights.sbomify.com/CVE-2016-10461/): Memory corruption in Snapdragon Mobile (critical 9.8)
- [CVE-2017-18135](https://insights.sbomify.com/CVE-2017-18135/): Memory corruption in Snapdragon Mobile (critical 9.8)
- [CVE-2017-18142](https://insights.sbomify.com/CVE-2017-18142/): Memory corruption in Snapdragon Mobile (critical 9.8)
- [CVE-2018-3589](https://insights.sbomify.com/CVE-2018-3589/): Memory corruption in Snapdragon Mobile (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-2256 is a critical code injection vulnerability in Qualcomm Mdm9650 Firmware, published on 14 Jun 2019. 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-2019-2256 in the wild and no public exploit code.

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

## Sources

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

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