# CVE-2019-10624: Integer overflow in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile

> Integer truncation in vendor command handling causes buffer overflow, potentially allowing code execution or privilege escalation on Qualcomm Snapdragon devices.

- **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:** 16 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-cw87-f64q-cj99

## What is CVE-2019-10624?

CVE-2019-10624 is a high-severity vulnerability in Qualcomm Apq8096au Firmware, published on 16 Apr 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

While handling the vendor command there is an integer truncation issue that could yield a buffer overflow due to int data type copied to u8 data type in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile in APQ8096AU, MSM8996AU, QCA6574AU, QCN7605, Rennell, SC8180X, SDM710, SDX55, SM7150, SM8150, SM8250, SXR2130

Weakness: CWE-681 (Incorrect Conversion between Numeric Types), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 12 products.


Products: Qualcomm Apq8096au Firmware, Qualcomm Msm8996au Firmware, Qualcomm Qca6574au Firmware, Qualcomm Qcn7605 Firmware, Qualcomm Rennell Firmware, Qualcomm Sc8180x Firmware, Qualcomm Sdm710 Firmware, Qualcomm Sdx55 Firmware, Qualcomm Sm7150 Firmware, Qualcomm Sm8150 Firmware, Qualcomm Sm8250 Firmware, Qualcomm Sxr2130 Firmware.

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

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

## Is CVE-2019-10624 being exploited?

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

## Other vulnerabilities in Qualcomm Apq8096au Firmware

- [CVE-2019-14045](https://insights.sbomify.com/CVE-2019-14045/): Memory corruption in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Mobile (critical 9.8)
- [CVE-2017-14911](https://insights.sbomify.com/CVE-2017-14911/): Auth bypass in Snapdragon IoT, Snapdragon Mobile, Snapdragon Automobile (critical 9.8)
- [CVE-2020-11126](https://insights.sbomify.com/CVE-2020-11126/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking (critical 9.1)
- [CVE-2022-33243](https://insights.sbomify.com/CVE-2022-33243/): Improper access control in Qualcomm IPC (high 8.4)
- [CVE-2022-22063](https://insights.sbomify.com/CVE-2022-22063/): Memory corruption in Core (high 8.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-10624 is a high-severity vulnerability in Qualcomm Apq8096au Firmware, published on 16 Apr 2020. 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-10624 in the wild and no public exploit code.

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

## Sources

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

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