# CVE-2019-2301: Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking

> Out-of-bounds read in Qualcomm Snapdragon firmware allows attackers to read memory or cause denial of service via SPI interface.

- **Severity:** High 7.8 (`CVSS:3.0/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:** 25 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-g7xv-jv8r-q9x7

## What is CVE-2019-2301?

CVE-2019-2301 is a high-severity memory corruption vulnerability in Qualcomm Ipq4019 Firmware, published on 25 Jul 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Possibility of out-of-bound read if id received from SPI is not in range of FIFO in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking in IPQ4019, IPQ8064, MSM8909W, MSM8996AU, QCA9980, QCS605, Qualcomm 215, SD 425, SD 439 / SD 429, SD 450, SD 625, SD 632, SD 636, SD 712 / SD 710 / SD 670, SD 820A, SD 845 / SD 850, SD 855, SDM439, SDM660, SDX24

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 24 products.


Products: Qualcomm Ipq4019 Firmware, Qualcomm Ipq8064 Firmware, Qualcomm Msm8909w Firmware, Qualcomm Msm8996au Firmware, Qualcomm Qca9980 Firmware, Qualcomm Qcs605 Firmware, Qualcomm Qualcomm 215 Firmware, Qualcomm Sd 425 Firmware, Qualcomm Sd 429 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 710 Firmware, Qualcomm Sd 712 Firmware, Qualcomm Sd 820a Firmware, Qualcomm Sd 845 Firmware, Qualcomm Sd 850 Firmware and 4 more.

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

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

## Is CVE-2019-2301 being exploited?

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

## Other vulnerabilities in Qualcomm Ipq4019 Firmware

- [CVE-2020-11172](https://insights.sbomify.com/CVE-2020-11172/): Memory corruption in Snapdragon Wired Infrastructure and Networking (critical 9.8)
- [CVE-2020-11117](https://insights.sbomify.com/CVE-2020-11117/): Command injection in Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Wired Infrastructure and Networking (critical 9.8)
- [CVE-2014-10045](https://insights.sbomify.com/CVE-2014-10045/): Memory corruption in Snapdragon Mobile, Snapdragon Wear (critical 9.8)
- [CVE-2014-9988](https://insights.sbomify.com/CVE-2014-9988/): Memory corruption in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear (critical 9.8)
- [CVE-2014-9998](https://insights.sbomify.com/CVE-2014-9998/): In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile, Snapdragon Mobile, and Snapdragon Wear IPQ40 (critical 9.8)

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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