# CVE-2019-2276: Memory corruption in Snapdragon Auto, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Mobile, Snapdragon Voice & Music

> An out-of-bounds read in Qualcomm Snapdragon firmware allows attackers to cause denial of service or disclose information via crafted beaconing requests.

- **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:** 25 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-269x-3w9j-5997

## What is CVE-2019-2276?

CVE-2019-2276 is a critical memory corruption vulnerability in Qualcomm Mdm9607 Firmware, published on 25 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Possible out of bound read occurs while processing beaconing request due to lack of check on action frames received from user controlled space in Snapdragon Auto, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Mobile, Snapdragon Voice & Music in MDM9607, MSM8996AU, QCA6174A, QCA6574AU, QCA9377, QCA9379, QCS405, QCS605, SD 636, SD 665, SD 675, SD 712 / SD 710 / SD 670, SD 730, SD 820A, SD 845 / SD 850, SD 855, SDM630, SDM660, SDX24

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

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

It affects 22 products.


Products: Qualcomm Mdm9607 Firmware, Qualcomm Msm8996au Firmware, Qualcomm Qca6174a Firmware, Qualcomm Qca6574au Firmware, Qualcomm Qca9377 Firmware, Qualcomm Qca9379 Firmware, Qualcomm Qcs405 Firmware, Qualcomm Qcs605 Firmware, Qualcomm Sd 636 Firmware, Qualcomm Sd 665 Firmware, Qualcomm Sd 670 Firmware, Qualcomm Sd 675 Firmware, Qualcomm Sd 710 Firmware, Qualcomm Sd 712 Firmware, Qualcomm Sd 730 Firmware, Qualcomm Sd 820a Firmware, Qualcomm Sd 845 Firmware, Qualcomm Sd 850 Firmware, Qualcomm Sd 855 Firmware, Qualcomm Sdm630 Firmware and 2 more.

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

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

## Is CVE-2019-2276 being exploited?

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

## Other vulnerabilities in Qualcomm Mdm9607 Firmware

- [CVE-2019-10531](https://insights.sbomify.com/CVE-2019-10531/): Memory corruption in Snapdragon Auto, Snapdragon Mobile, Snapdragon Wearables (critical 9.8)
- [CVE-2018-5915](https://insights.sbomify.com/CVE-2018-5915/): Denial of service in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear (critical 9.8)
- [CVE-2015-9126](https://insights.sbomify.com/CVE-2015-9126/): Memory corruption in Snapdragon Mobile, Snapdragon Wear (critical 9.8)
- [CVE-2016-10479](https://insights.sbomify.com/CVE-2016-10479/): Memory corruption in Snapdragon Mobile (critical 9.8)
- [CVE-2016-10481](https://insights.sbomify.com/CVE-2016-10481/): Null dereference in Snapdragon Mobile, Snapdragon Wear (critical 9.8)

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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