# CVE-2019-2248: Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables

> A buffer overflow in Qualcomm Snapdragon firmware allows attackers to execute arbitrary code or escalate privileges via invalid headers.

- **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:** 24 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-j52m-wj96-vpr2

## What is CVE-2019-2248?

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

### Official description

Buffer overflow can occur if invalid header tries to overwrite the existing buffer which fix size allocation in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in MDM9150, MDM9206, MDM9607, MDM9650, MSM8909W, MSM8996AU, Qualcomm 215, SD 210/SD 212/SD 205, SD 425, SD 427, SD 430, SD 435, SD 439 / SD 429, SD 450, SD 615/16/SD 415, SD 625, SD 632, SD 636, SD 650/52, SD 820, SD 820A, SD 845 / SD 850, SDM439, SDM660, SDX20

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 33 products.


Products: Qualcomm 215 Firmware, Qualcomm Mdm9150 Firmware, Qualcomm Mdm9206 Firmware, Qualcomm Mdm9607 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Msm8909w Firmware, Qualcomm Msm8996au Firmware, Qualcomm Qm215 Firmware, Qualcomm Sd 205 Firmware, Qualcomm Sd 210 Firmware, Qualcomm Sd 212 Firmware, Qualcomm Sd 415 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 615 Firmware and 13 more.

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

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

## Is CVE-2019-2248 being exploited?

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

## Other vulnerabilities in Qualcomm Mdm9150 Firmware

- [CVE-2024-53014](https://insights.sbomify.com/CVE-2024-53014/): Improper Validation of Array Index in Audio (high 7.8)
- [CVE-2025-21424](https://insights.sbomify.com/CVE-2025-21424/): Use After Free in NPU (high 7.8)
- [CVE-2023-22386](https://insights.sbomify.com/CVE-2023-22386/): Buffer Copy Without Checking Size of Input in WLAN HOST (high 7.8)
- [CVE-2023-24854](https://insights.sbomify.com/CVE-2023-24854/): Stack-based Buffer Overflow in WLAN HOST (high 7.8)
- [CVE-2018-11922](https://insights.sbomify.com/CVE-2018-11922/): Configurations in Android Build (high 7.5)

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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