CVE-2017-18321
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 used by the terminal and NW for a session could be leaked in snapdragon mobile in versions MDM9650, MDM9655, SD 835, SDA660.
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 confidenceSession security keys used between the mobile terminal and network could be leaked in affected Qualcomm Snapdragon chipsets (MDM9650, MDM9655, SD 835, SDA660). This is a cryptographic key exposure vulnerability in the baseband/modem component that could allow session hijacking or man-in-the-middle attacks.
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 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 the chipset model in your deviceCheck your device specifications or system information to determine if the chipset is one of: MDM9650, MDM9655, SD 835, or SDA660. On Android, this is often found under Settings > About Phone > Chipset or via commands like 'getprop ro.board.platform' or 'cat /proc/cpuinfo'. On iOS devices, this information is not typically exposed as they use different modems.Affected if The device contains any of the four affected chipset models (MDM9650, MDM9655, SD 835, SDA660)
-
Verify baseband/modem firmware versionCheck the baseband firmware version on the device. On Android, this can typically be found under Settings > About Phone > Baseband Version, or via the command 'getprop gsm.version.baseband' or 'service call iphonesubinfo 1 | grep -o "[0-9a-f]\{8\}" | tail -n 1'. Some devices also expose this in /proc/cmdline or through diagnostic menus (Engineering Mode).Affected if The baseband firmware version corresponds to the affected chipset models listed (MDM9650, MDM9655, SD 835, SDA660)
-
Confirm the device uses an affected Qualcomm modem componentCheck if the device utilizes a Qualcomm baseband modem for cellular connectivity. This can be verified by examining the modem firmware files in /firmware or /vendor/firmware, or by checking kernel logs for references to 'qcom', 'mdm', or 'Snapdragon' modem components. Devices with alternative modems (e.g., Intel, MediaTek, Samsung) are not affected.Affected if The device uses a Qualcomm baseband/modem component and the specific chipset model matches one of the four affected variants
Your environment is affected if any device contains a Qualcomm Snapdragon chipset model MDM9650, MDM9655, SD 835, or SDA660 with cellular connectivity enabled, as the cryptographic key exposure exists in all firmware versions of these chipsets.
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/security updates provided by Qualcomm and downstream device OEMs. Until patches are available, consider network-level controls such as VPN usage on affected devices to reduce exposure window.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18321 — 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-18321 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