# CVE-2019-14068: Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking

> Out-of-bounds access in Qualcomm Snapdragon routing allows attackers to execute arbitrary code or escalate privileges via crafted inputs.

- **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:** 5 Mar 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-ww6v-h9jg-qx5w

## What is CVE-2019-14068?

CVE-2019-14068 is a high-severity memory corruption vulnerability in Qualcomm Apq8009 Firmware, published on 5 Mar 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Out of bound access in msm routing due to lack of check of size before accessing in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking in APQ8009, APQ8053, APQ8096AU, MDM9607, MSM8905, MSM8909W, Nicobar, QCS405, QCS605, Rennell, Saipan, SDM429W, SDM845, SDX20, SDX24, SM6150, SM7150, SM8150, SM8250, SXR1130, SXR2130

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 21 products.


Products: Qualcomm Apq8009 Firmware, Qualcomm Apq8053 Firmware, Qualcomm Apq8096au Firmware, Qualcomm Mdm9607 Firmware, Qualcomm Msm8905 Firmware, Qualcomm Msm8909w Firmware, Qualcomm Nicobar Firmware, Qualcomm Qcs405 Firmware, Qualcomm Qcs605 Firmware, Qualcomm Rennell Firmware, Qualcomm Saipan Firmware, Qualcomm Sdm429w Firmware, Qualcomm Sdm845 Firmware, Qualcomm Sdx20 Firmware, Qualcomm Sdx24 Firmware, Qualcomm Sm6150 Firmware, Qualcomm Sm7150 Firmware, Qualcomm Sm8150 Firmware, Qualcomm Sm8250 Firmware, Qualcomm Sxr1130 Firmware and 1 more.

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

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

## Is CVE-2019-14068 being exploited?

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

## Other vulnerabilities in Qualcomm Apq8009 Firmware

- [CVE-2021-1905](https://insights.sbomify.com/CVE-2021-1905/): Qualcomm Multiple Chipsets Use-After-Free (high 8.4, exploited in the wild)
- [CVE-2020-11261](https://insights.sbomify.com/CVE-2020-11261/): Qualcomm Multiple Chipsets Improper Input Validation (high 7.8, exploited in the wild)
- [CVE-2021-1906](https://insights.sbomify.com/CVE-2021-1906/): Qualcomm Multiple Chipsets Detection of Error Condition Without Action (medium 6.2, exploited in the wild)
- [CVE-2022-40510](https://insights.sbomify.com/CVE-2022-40510/): Buffer copy without checking size of input in Audio. (critical 9.8)
- [CVE-2022-22088](https://insights.sbomify.com/CVE-2022-22088/): Integer Overflow to Buffer Overflow in Bluetooth HOST (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-14068 is a high-severity memory corruption vulnerability in Qualcomm Apq8009 Firmware, published on 5 Mar 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-14068 in the wild and no public exploit code.

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

## Sources

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

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