# CVE-2019-10484: Use after free in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables

> A use-after-free vulnerability in Qualcomm Snapdragon firmware allows attackers to execute arbitrary code or escalate privileges via command destructors.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:** 12 Dec 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9hj8-x5gx-9x3m

## What is CVE-2019-10484?

CVE-2019-10484 is a medium-severity use after free vulnerability in Qualcomm Apq8098 Firmware, published on 12 Dec 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Use after free issue occurs when command destructors access dynamically allocated response buffer which is already deallocated during previous command teardwon sequence in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in APQ8098, MSM8909W, Nicobar, QCS405, QCS605, SDA845, SDM660, SDM670, SDM710, SDM845, SDX24, SM6150, SM7150, SM8150, SM8250, SXR2130

Weakness: CWE-416 (Use After Free)

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

It affects 16 products.


Products: Qualcomm Apq8098 Firmware, Qualcomm Msm8909w Firmware, Qualcomm Nicobar Firmware, Qualcomm Qcs405 Firmware, Qualcomm Qcs605 Firmware, Qualcomm Sda845 Firmware, Qualcomm Sdm660 Firmware, Qualcomm Sdm670 Firmware, Qualcomm Sdm710 Firmware, Qualcomm Sdm845 Firmware, Qualcomm Sdx24 Firmware, Qualcomm Sm6150 Firmware, Qualcomm Sm7150 Firmware, Qualcomm Sm8150 Firmware, Qualcomm Sm8250 Firmware, Qualcomm Sxr2130 Firmware.

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

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

## Is CVE-2019-10484 being exploited?

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

## Other vulnerabilities in Qualcomm Apq8098 Firmware

- [CVE-2020-3667](https://insights.sbomify.com/CVE-2020-3667/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking (critical 9.8)
- [CVE-2020-3669](https://insights.sbomify.com/CVE-2020-3669/): 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.8)
- [CVE-2019-14112](https://insights.sbomify.com/CVE-2019-14112/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking (critical 9.8)
- [CVE-2019-14086](https://insights.sbomify.com/CVE-2019-14086/): Integer overflow in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile (critical 9.8)
- [CVE-2020-11206](https://insights.sbomify.com/CVE-2020-11206/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-10484 is a medium-severity use after free vulnerability in Qualcomm Apq8098 Firmware, published on 12 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-10484 in the wild and no public exploit code.

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

## Sources

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

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