# CVE-2019-14130: Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking

> Memory corruption in Qualcomm Snapdragon firmware allows attackers to execute arbitrary code or escalate privileges via malformed buffer offsets.

- **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:** 30 Jul 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-f692-3mc6-m68j

## What is CVE-2019-14130?

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

### Official description

Memory corruption can occurs in trusted application if offset size from HLOS is more than actual mapped buffer size in Snapdragon Auto, Snapdragon Compute, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking in Kamorta, QCS404, Rennell, SC7180, SDX55, SM6150, SM7150, SM8250, SXR2130

Weakness: CWE-787 (Out-of-bounds Write), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 9 products.


Products: Qualcomm Kamorta Firmware, Qualcomm Qcs404 Firmware, Qualcomm Rennell Firmware, Qualcomm Sc7180 Firmware, Qualcomm Sdx55 Firmware, Qualcomm Sm6150 Firmware, Qualcomm Sm7150 Firmware, Qualcomm Sm8250 Firmware, Qualcomm Sxr2130 Firmware.

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

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

## Is CVE-2019-14130 being exploited?

There is no known exploitation of CVE-2019-14130 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-14130 and fix it if it is affected.

What it is: CVE-2019-14130 is a high-severity memory corruption vulnerability in Qualcomm Kamorta Firmware, published on 30 Jul 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-14130 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-14130/ (Markdown: https://insights.sbomify.com/CVE-2019-14130/index.md)
```

## Sources

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

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