# CVE-2019-14008: Null dereference in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile

> A missing null check in location assistance data processing allows attackers to cause a denial of service on Qualcomm Snapdragon devices.

- **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:** 21 Jan 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-vcxh-qw7p-r93v

## What is CVE-2019-14008?

CVE-2019-14008 is a high-severity vulnerability in Qualcomm Mdm9150 Firmware, published on 21 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Possible null pointer dereference issue in location assistance data processing due to missing null check on resources before using it in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile in MDM9150, MDM9607, MDM9650, SDM660, SDM845, SM8150, SM8250, SXR2130

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 8 products.


Products: Qualcomm Mdm9150 Firmware, Qualcomm Mdm9607 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Sdm660 Firmware, Qualcomm Sdm845 Firmware, Qualcomm Sm8150 Firmware, Qualcomm Sm8250 Firmware, Qualcomm Sxr2130 Firmware.

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

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

## Is CVE-2019-14008 being exploited?

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

## Other vulnerabilities in Qualcomm Mdm9150 Firmware

- [CVE-2019-10505](https://insights.sbomify.com/CVE-2019-10505/): Memory corruption in Snapdragon Auto, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)
- [CVE-2019-10542](https://insights.sbomify.com/CVE-2019-10542/): Memory corruption in Snapdragon Auto, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music (critical 9.8)
- [CVE-2019-2258](https://insights.sbomify.com/CVE-2019-2258/): Memory corruption 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-2283](https://insights.sbomify.com/CVE-2019-2283/): 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-2323](https://insights.sbomify.com/CVE-2019-2323/): Null dereference in Snapdragon Auto, Snapdragon Compute, 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-14008 and fix it if it is affected.

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

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

## Sources

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

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