# CVE-2019-14066: Integer overflow in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking

> An integer overflow in Qualcomm Snapdragon firmware allows attackers to potentially execute arbitrary code or escalate privileges via feature ID checks.

- **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-3qg4-vrhv-p2hp

## What is CVE-2019-14066?

CVE-2019-14066 is a high-severity vulnerability in Qualcomm Kamorta 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

Integer overflow in calculating estimated output buffer size when getting a list of installed Feature IDs, Serial Numbers or checking Feature ID status in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking in Kamorta, MDM9205, MDM9607, Nicobar, QCS404, QCS405, Rennell, SA6155P, SC7180, SC8180X, SDX55, SM6150, SM7150, SXR2130

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 14 products.


Products: Qualcomm Kamorta Firmware, Qualcomm Mdm9205 Firmware, Qualcomm Mdm9607 Firmware, Qualcomm Nicobar Firmware, Qualcomm Qcs404 Firmware, Qualcomm Qcs405 Firmware, Qualcomm Rennell Firmware, Qualcomm Sa6155p Firmware, Qualcomm Sc7180 Firmware, Qualcomm Sc8180x Firmware, Qualcomm Sdx55 Firmware, Qualcomm Sm6150 Firmware, Qualcomm Sm7150 Firmware, Qualcomm Sxr2130 Firmware.

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

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

## Is CVE-2019-14066 being exploited?

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

## Other vulnerabilities in Qualcomm Kamorta Firmware

- [CVE-2019-14056](https://insights.sbomify.com/CVE-2019-14056/): Integer overflow in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking (high 7.8)
- [CVE-2019-14089](https://insights.sbomify.com/CVE-2019-14089/): Security feature bypass in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking (high 7.8)
- [CVE-2020-3636](https://insights.sbomify.com/CVE-2020-3636/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking (high 7.8)
- [CVE-2019-14123](https://insights.sbomify.com/CVE-2019-14123/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking (high 7.8)
- [CVE-2019-14124](https://insights.sbomify.com/CVE-2019-14124/): Null dereference in Snapdragon Auto, Snapdragon Compute, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-14066 is a high-severity vulnerability in Qualcomm Kamorta 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-14066 in the wild and no public exploit code.

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

## Sources

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

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