# CVE-2019-2304: Integer overflow in Snapdragon Auto, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking

> An integer overflow in Qualcomm Snapdragon firmware allows attackers to trigger a buffer overflow, potentially leading to arbitrary code execution.

- **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:** 18 Dec 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-h9wh-f73q-fp87

## What is CVE-2019-2304?

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

### Official description

Integer overflow to buffer overflow due to lack of validation of event arguments received from firmware. in Snapdragon Auto, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking in IPQ4019, IPQ8064, IPQ8074, MDM9607, MSM8917, MSM8920, MSM8937, MSM8940, QCN7605, QCS405, QCS605, SDA845, SDM660, SDM845, SDX24, SDX55, SM6150, SM7150, SM8150, SXR1130

Weakness: CWE-787 (Out-of-bounds Write), CWE-20 (Improper Input Validation), CWE-190 (Integer Overflow or Wraparound)

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

It affects 20 products.


Products: Qualcomm Ipq4019 Firmware, Qualcomm Ipq8064 Firmware, Qualcomm Ipq8074 Firmware, Qualcomm Mdm9607 Firmware, Qualcomm Msm8917 Firmware, Qualcomm Msm8920 Firmware, Qualcomm Msm8937 Firmware, Qualcomm Msm8940 Firmware, Qualcomm Qcn7605 Firmware, Qualcomm Qcs405 Firmware, Qualcomm Qcs605 Firmware, Qualcomm Sda845 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-2304?

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

## Is CVE-2019-2304 being exploited?

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

What it is: CVE-2019-2304 is a high-severity vulnerability in Qualcomm Ipq4019 Firmware, published on 18 Dec 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-2304 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-2304/ (Markdown: https://insights.sbomify.com/CVE-2019-2304/index.md)
```

## Sources

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

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