# CVE-2017-14910: Memory corruption in Snapdragon Automobile, Snapdragon IoT, Snapdragon Mobile

> A buffer overread in Qualcomm Snapdragon firmware allows attackers to cause denial of service or disclose information via crafted input files.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 23 Feb 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-82hw-cp64-7hhp

## What is CVE-2017-14910?

CVE-2017-14910 is a critical memory corruption vulnerability in Qualcomm Mdm9206 Firmware, published on 23 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Snapdragon Automobile, Snapdragon IoT and Snapdragon Mobile MDM9206 MDM9607, MDM9650, S820A, S820Am, SD 210/SD 212/SD 205, SD 410/12, SD 425, SD 430, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 820, SD 835, and SD 845, a buffer overread is possible if there are no newlines in an input file.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2017-14910?

It affects 21 products.


Products: Qualcomm Mdm9206 Firmware, Qualcomm Mdm9607 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm S820a Firmware, Qualcomm S820am Firmware, Qualcomm Sd 210 Firmware, Qualcomm Sd 212 Firmware, Qualcomm Sd 410 Firmware, Qualcomm Sd 412 Firmware, Qualcomm Sd 415 Firmware, Qualcomm Sd 425 Firmware, Qualcomm Sd 430 Firmware, Qualcomm Sd 615 Firmware, Qualcomm Sd 616 Firmware, Qualcomm Sd 617 Firmware, Qualcomm Sd 625 Firmware, Qualcomm Sd 650 Firmware, Qualcomm Sd 652 Firmware, Qualcomm Sd 820 Firmware, Qualcomm Sd 835 Firmware and 1 more.

## How do I fix CVE-2017-14910?

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

## Is CVE-2017-14910 being exploited?

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

## Other vulnerabilities in Qualcomm Mdm9206 Firmware

- [CVE-2016-10394](https://insights.sbomify.com/CVE-2016-10394/): Improper Authentication in Core (critical 9.8)
- [CVE-2019-10522](https://insights.sbomify.com/CVE-2019-10522/): 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-10528](https://insights.sbomify.com/CVE-2019-10528/): Use after free in Snapdragon Auto, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)
- [CVE-2019-10533](https://insights.sbomify.com/CVE-2019-10533/): 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-10534](https://insights.sbomify.com/CVE-2019-10534/): 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-2017-14910 and fix it if it is affected.

What it is: CVE-2017-14910 is a critical memory corruption vulnerability in Qualcomm Mdm9206 Firmware, published on 23 Feb 2018. 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-2017-14910 in the wild and no public exploit code.

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

## Sources

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

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