CVE-2017-18332
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSecurity 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
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceSecurity keys used for WCDMA call encryption are being written to system logs during call configuration or reconfiguration on affected Qualcomm Snapdragon chipsets. An attacker with access to device logs could recover these cryptographic keys and potentially compromise the confidentiality of WCDMA communications.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify chipset modelCheck device info or run 'cat /proc/cpuinfo' or check 'getprop' (Android) to determine the Qualcomm chipset model (e.g., Mdm9607, Msm8909w, etc.)Affected if Chipset matches any of the affected models: Mdm9607, Mdm9635m, Mdm9640, Mdm9645, Mdm9650, Mdm9655, Msm8909w, Msm8996au
-
Verify WCDMA capability is enabledCheck if the device supports or has WCDMA (3G) calling enabled - look for 'WCDMA', 'UMTS', or '3G' in radio/carrier configuration or settingsAffected if WCDMA calling feature is active or configurable on the device
-
Examine system logs for key exposureReview system logs (logcat, dmesg, /data/log/, or vendor-specific log partitions) for patterns resembling cryptographic key material appearing during or after call setup events. Search for hexadecimal strings of appropriate key length near 'WCDMA', 'call', 'encryption', or 'key' indicators.Affected if Logs contain any readable WCDMA encryption key material (long hexadecimal strings) in proximity to call configuration events
-
Check log retention and accessInspect where device logs are stored and whether they persist across reboots. Verify if logs are accessible to apps or via adb debugging.Affected if Logs containing potential key material are retained and accessible beyond the call session
Device is affected if it uses any of the listed Qualcomm chipsets, has WCDMA calling enabled, and system logs contain exposed WCDMA encryption key material from call configuration events.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply firmware updates from Qualcomm or device OEM manufacturers for affected chipsets to prevent security key logging; audit existing logs for potential key exposure.
- Consultation6.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18332 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-18332 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data