# CVE-2019-14012: Null dereference in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables

> A null pointer dereference in Qualcomm Snapdragon firmware allows attackers to cause a denial of service via crafted SDP messages.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 16 Apr 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-m474-22p6-39cr

## What is CVE-2019-14012?

CVE-2019-14012 is a high-severity vulnerability in Qualcomm Msm8905 Firmware, published on 16 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Possibility of null pointer deference as the array of video codecs from media info is referenced without null checking while processing SDP messages in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables in MSM8905, MSM8909, MSM8917, MSM8920, MSM8937, MSM8940, MSM8953, Nicobar, QCM2150, QM215, Rennell, SC7180, SC8180X, SDA845, SDM429, SDM439, SDM450, SDM632, SDM845, SDM850, SDX24, SM6150, SM7150, SM8150

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 24 products.


Products: Qualcomm Msm8905 Firmware, Qualcomm Msm8909 Firmware, Qualcomm Msm8917 Firmware, Qualcomm Msm8920 Firmware, Qualcomm Msm8937 Firmware, Qualcomm Msm8940 Firmware, Qualcomm Msm8953 Firmware, Qualcomm Nicobar Firmware, Qualcomm Qcm2150 Firmware, Qualcomm Qm215 Firmware, Qualcomm Rennell Firmware, Qualcomm Sc7180 Firmware, Qualcomm Sc8180x Firmware, Qualcomm Sda845 Firmware, Qualcomm Sdm429 Firmware, Qualcomm Sdm439 Firmware, Qualcomm Sdm450 Firmware, Qualcomm Sdm632 Firmware, Qualcomm Sdm845 Firmware, Qualcomm Sdm850 Firmware and 4 more.

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

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

## Is CVE-2019-14012 being exploited?

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

## Other vulnerabilities in Qualcomm Msm8905 Firmware

- [CVE-2019-2317](https://insights.sbomify.com/CVE-2019-2317/): Weak cryptography in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)
- [CVE-2019-10549](https://insights.sbomify.com/CVE-2019-10549/): Null dereference in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables (high 7.5)

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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