# CVE-2019-14087: Use after free in Snapdragon Consumer IOT, Snapdragon Mobile, Snapdragon Wearables

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

- **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:** 2 Jun 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-5cf3-xv24-528h

## What is CVE-2019-14087?

CVE-2019-14087 is a high-severity use after free vulnerability in Qualcomm Msm8909w Firmware, published on 2 Jun 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Failure in buffer management while accessing handle for HDR blit when color modes not supported by display in Snapdragon Consumer IOT, Snapdragon Mobile, Snapdragon Wearables in MSM8909W, QCS605

Weakness: CWE-416 (Use After Free)

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

It affects 2 products.


Products: Qualcomm Msm8909w Firmware, Qualcomm Qcs605 Firmware.

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

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

## Is CVE-2019-14087 being exploited?

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

## Other vulnerabilities in Qualcomm Msm8909w Firmware

- [CVE-2019-2285](https://insights.sbomify.com/CVE-2019-2285/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)
- [CVE-2019-10509](https://insights.sbomify.com/CVE-2019-10509/): Use after free in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)
- [CVE-2019-10538](https://insights.sbomify.com/CVE-2019-10538/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)
- [CVE-2019-2255](https://insights.sbomify.com/CVE-2019-2255/): Code injection in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)
- [CVE-2019-2259](https://insights.sbomify.com/CVE-2019-2259/): Denial of service in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-14087 is a high-severity use after free vulnerability in Qualcomm Msm8909w Firmware, published on 2 Jun 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-14087 in the wild and no public exploit code.

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

## Sources

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

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