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

> An integer underflow in Qualcomm Snapdragon firmware allows attackers to cause a denial of service via malformed SDF frames.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 5 Mar 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-429h-653h-9h2w

## What is CVE-2019-14083?

CVE-2019-14083 is a critical vulnerability in Qualcomm Apq8009 Firmware, published on 5 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

While parsing Service Descriptor Extended Attribute received as part of SDF frame, there is a possibility that incorrect length is specified in the attribute length field of extended SSI which can lead to integer underflow in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking in APQ8009, APQ8053, APQ8096, APQ8098, IPQ6018, IPQ8074, MSM8996AU, MSM8998, Nicobar, QCA6174A, QCA6390, QCA6574AU, QCA8081, QCA9377, QCA9379, QCN7605, QCS404, QCS405, QCS605, Rennell, SC8180X, SDA660, SDA845, SDM630, SDM636, SDM660, SDM670, SDM710, SDM845, SDM850, SDX20, SDX24, SM6150, SM7150, SM8150, SXR1130, SXR2130

Weakness: CWE-191 (Integer Underflow (Wrap or Wraparound))

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

It affects 37 products.


Products: Qualcomm Apq8009 Firmware, Qualcomm Apq8053 Firmware, Qualcomm Apq8096 Firmware, Qualcomm Apq8098 Firmware, Qualcomm Ipq6018 Firmware, Qualcomm Ipq8074 Firmware, Qualcomm Msm8996au Firmware, Qualcomm Msm8998 Firmware, Qualcomm Nicobar Firmware, Qualcomm Qca6174a Firmware, Qualcomm Qca6390 Firmware, Qualcomm Qca6574au Firmware, Qualcomm Qca8081 Firmware, Qualcomm Qca9377 Firmware, Qualcomm Qca9379 Firmware, Qualcomm Qcn7605 Firmware, Qualcomm Qcs404 Firmware, Qualcomm Qcs405 Firmware, Qualcomm Qcs605 Firmware, Qualcomm Rennell Firmware and 17 more.

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

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

## Is CVE-2019-14083 being exploited?

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

What it is: CVE-2019-14083 is a critical vulnerability in Qualcomm Apq8009 Firmware, published on 5 Mar 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-14083 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-14083/ (Markdown: https://insights.sbomify.com/CVE-2019-14083/index.md)
```

## Sources

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

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