# CVE-2017-18280: Information disclosure in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear

> A Trusted Application can read data from an open SPI/I2C interface accessed by another Trusted Application, leading to information disclosure.

- **Severity:** High 7.8 (`CVSS:3.0/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:** 20 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-985h-j93g-9259

## What is CVE-2017-18280?

CVE-2017-18280 is a high-severity vulnerability in Qualcomm Mdm9607 Firmware, published on 20 Sep 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In Snapdragon (Automobile, Mobile, Wear) in version MDM9607, MSM8909W, MSM8996AU, SD 210/SD 212/SD 205, SD 425, SD 427, SD 430, SD 435, SD 450, SD 617, SD 625, SD 650/52, SD 820, SD 820A, SD 835, SDM429, SDM439, SDM632, Snapdragon_High_Med_2016, when a Trusted Application has opened the SPI/I2C interface to a particular device, it is possible for another Trusted Application to read the data on this open interface by calling the SPI/I2C read function.

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

It affects 21 products.


Products: Qualcomm Mdm9607 Firmware, Qualcomm Msm8909w Firmware, Qualcomm Msm8996au Firmware, Qualcomm Sd205 Firmware, Qualcomm Sd210 Firmware, Qualcomm Sd212 Firmware, Qualcomm Sd425 Firmware, Qualcomm Sd427 Firmware, Qualcomm Sd430 Firmware, Qualcomm Sd435 Firmware, Qualcomm Sd450 Firmware, Qualcomm Sd617 Firmware, Qualcomm Sd625 Firmware, Qualcomm Sd650 Firmware, Qualcomm Sd652 Firmware, Qualcomm Sd820 Firmware, Qualcomm Sd820a Firmware, Qualcomm Sd835 Firmware, Qualcomm Sdm429 Firmware, Qualcomm Sdm439 Firmware and 1 more.

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

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

## Is CVE-2017-18280 being exploited?

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

## Other vulnerabilities in Qualcomm Mdm9607 Firmware

- [CVE-2019-10531](https://insights.sbomify.com/CVE-2019-10531/): Memory corruption in Snapdragon Auto, Snapdragon Mobile, Snapdragon Wearables (critical 9.8)
- [CVE-2019-2276](https://insights.sbomify.com/CVE-2019-2276/): Memory corruption in Snapdragon Auto, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Mobile, Snapdragon Voice & Music (critical 9.8)
- [CVE-2018-5915](https://insights.sbomify.com/CVE-2018-5915/): Denial of service in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear (critical 9.8)
- [CVE-2015-9126](https://insights.sbomify.com/CVE-2015-9126/): Memory corruption in Snapdragon Mobile, Snapdragon Wear (critical 9.8)
- [CVE-2016-10479](https://insights.sbomify.com/CVE-2016-10479/): Memory corruption in Snapdragon Mobile (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-18280 and fix it if it is affected.

What it is: CVE-2017-18280 is a high-severity vulnerability in Qualcomm Mdm9607 Firmware, published on 20 Sep 2018. 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-2017-18280 in the wild and no public exploit code.

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

## Sources

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

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