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

> Stack overflow in UTCB object allows corruption of function pointers, potentially enabling arbitrary code execution on Qualcomm Snapdragon devices.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 5 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-932h-4f26-84hm

## What is CVE-2019-10612?

CVE-2019-10612 is a critical memory corruption vulnerability in Qualcomm Mdm9205 Firmware, published on 5 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

UTCB object has a function pointer called by the reaper to deallocate its memory resources and this address can potentially be corrupted by stack overflow in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking in MDM9205, MDM9650, QCS605, SA6155P, SC8180X, SDA845, SDM670, SDM710, SDM845, SDM850, SDX55, SM6150, SM7150, SM8150, SM8250, SXR1130, SXR2130

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 17 products.


Products: Qualcomm Mdm9205 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Qcs605 Firmware, Qualcomm Sa6155p Firmware, Qualcomm Sc8180x Firmware, Qualcomm Sda845 Firmware, Qualcomm Sdm670 Firmware, Qualcomm Sdm710 Firmware, Qualcomm Sdm845 Firmware, Qualcomm Sdm850 Firmware, Qualcomm Sdx55 Firmware, Qualcomm Sm6150 Firmware, Qualcomm Sm7150 Firmware, Qualcomm Sm8150 Firmware, Qualcomm Sm8250 Firmware, Qualcomm Sxr1130 Firmware, Qualcomm Sxr2130 Firmware.

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

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

## Is CVE-2019-10612 being exploited?

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

## Other vulnerabilities in Qualcomm Mdm9205 Firmware

- [CVE-2022-25745](https://insights.sbomify.com/CVE-2022-25745/): Always Incorrect Control Flow Implementation in MODEM (critical 9.8)
- [CVE-2019-2294](https://insights.sbomify.com/CVE-2019-2294/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)
- [CVE-2020-11127](https://insights.sbomify.com/CVE-2020-11127/): Integer overflow in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking (high 7.8)
- [CVE-2019-14030](https://insights.sbomify.com/CVE-2019-14030/): Integer overflow in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking (high 7.8)
- [CVE-2019-2267](https://insights.sbomify.com/CVE-2019-2267/): Missing authorization in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-10612 is a critical memory corruption vulnerability in Qualcomm Mdm9205 Firmware, published on 5 Mar 2020. 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-10612 in the wild and no public exploit code.

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

## Sources

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

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