CVE-2017-18308
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 · uneditedModem segments are unlocked after authentication, leaving modem segments open to all in Snapdragon Mobile, Snapdragon Wear in version MDM9607, MSM8909W, SD 210/SD 212/SD 205, SD 425, SD 430
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 confidenceThis vulnerability exists in the modem/baseband subsystem of affected Qualcomm Snapdragon chipsets. After the authentication process completes, modem segments remain in an unlocked state rather than re-locking, potentially allowing unauthorized access to sensitive modem functions and data.
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 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
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 modelCheck the device hardware specifications, bootloader info, or system-on-chip (SoC) details to determine if the chipset is one of: Mdm9607, Msm8909w, Sd 210, Sd 212, Sd 205, Sd 425, or Sd 430. On Android devices, this is typically found under Settings > About Phone > Baseband or under /proc/cpuinfo.Affected if The chipset model matches any of the affected Qualcomm Snapdragon models listed above.
-
Check the modem/baseband firmware versionRetrieve the baseband/modem firmware version from the device. On Android, this is often visible in Settings > About Phone > Baseband version, or via AT command 'AT+CGMR' when connected to the modem serial interface, or through the qmi-proxy diagnostic interface.Affected if The baseband firmware version corresponds to any of the affected chipset firmware releases (Mdm9607, Msm8909w, Sd 210, Sd 212, Sd 205, Sd 425, Sd 430).
-
Confirm the authentication state vulnerabilityThis specific vulnerability requires inspection of the modem authentication state after a successful authentication cycle. This typically requires access to the modem debug interface or OEM diagnostic tools that can query the modem security state (locked/unlocked segments). Consult OEM documentation for vendor-specific diagnostic commands.Affected if The device shows that modem segments remain in an unlocked state after authentication completes, rather than returning to a locked state.
If the device uses any of the affected Qualcomm chipset models (Mdm9607, Msm8909w, Sd 210, Sd 212, Sd 205, Sd 425, Sd 430) with the associated modem/baseband firmware, the device is vulnerable to this authentication bypass issue.
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 vendor-supplied firmware updates from the device/OEM manufacturer. Contact the device vendor or carrier for patched firmware releases addressing this modem authentication bypass issue.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18308 — 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-18308 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