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

> Security keys are logged during WCDMA call configuration in Qualcomm Snapdragon firmware, potentially exposing sensitive cryptographic material to attackers with log access.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 18 Jan 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xprp-4qjc-gqwc

## What is CVE-2017-18332?

CVE-2017-18332 is a medium-severity vulnerability in Qualcomm Mdm9607 Firmware, published on 18 Jan 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Security keys are logged when any WCDMA call is configured or reconfigured in snapdragon automobile, snapdragon mobile and snapdragon wear in versions MDM9607, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8909W, MSM8996AU, SD 210/SD 212/SD 205, SD 425, SD 430, SD 450, SD 625, SD 650/52, SD 712 / SD 710 / SD 670, SD 820, SD 820A, SD 835, SD 845 / SD 850, SDA660, SDX20, SXR1130

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 28 products.


Products: Qualcomm Mdm9607 Firmware, Qualcomm Mdm9635m Firmware, Qualcomm Mdm9640 Firmware, Qualcomm Mdm9645 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Mdm9655 Firmware, Qualcomm Msm8909w Firmware, Qualcomm Msm8996au Firmware, Qualcomm Sd 205 Firmware, Qualcomm Sd 210 Firmware, Qualcomm Sd 212 Firmware, Qualcomm Sd 425 Firmware, Qualcomm Sd 430 Firmware, Qualcomm Sd 450 Firmware, Qualcomm Sd 625 Firmware, Qualcomm Sd 650 Firmware, Qualcomm Sd 652 Firmware, Qualcomm Sd 670 Firmware, Qualcomm Sd 710 Firmware, Qualcomm Sd 712 Firmware and 8 more.

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

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

## Is CVE-2017-18332 being exploited?

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

What it is: CVE-2017-18332 is a medium-severity vulnerability in Qualcomm Mdm9607 Firmware, published on 18 Jan 2019. 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-18332 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-18332/ (Markdown: https://insights.sbomify.com/CVE-2017-18332/index.md)
```

## Sources

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

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