CVE-2017-18293
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 · uneditedWhen a particular GPIO is protected by blocking access to the corresponding GPIO resource registers, the protection can be bypassed using the corresponding banked GPIO registers instead in Snapdragon Mobile, Snapdragon Wear in version MDM9206, MDM9607, MDM9650, SD 210/SD 212/SD 205, SD 425, SD 430, SD 450, SD 625, SD 650/52, 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 · high confidenceGPIO resource protection can be bypassed by using banked GPIO registers instead of the standard GPIO resource registers on affected Snapdragon chipsets, allowing unauthorized access to protected GPIO pins.
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
- 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 chipset modelCheck the processor/hardware identifier via /proc/cpuinfo on Android or embedded Linux, or check BIOS/UEFI for Snapdragon module infoAffected if The chipset model matches Mdm9206, Mdm9607, Mdm9650, Sd 210, Sd 212, Sd 205, Sd 425, or Sd 430
-
Verify firmware versionRetrieve firmware version via 'cat /proc/version' or vendor-specific AT commands (for modems) or through the bootloaderAffected if The firmware version corresponds to any version on the affected chipset models (all versions are vulnerable)
-
Confirm GPIO subsystem is accessibleCheck for /sys/class/gpio presence and read access to GPIO bank registers in /sys/devices or via raw memory mapping of GPIO hardware blockAffected if Banked GPIO register access is available and readable without elevated privileges
-
Check GPIO permission settingsInspect /sys/class/gpio/*/permission or device tree bindings for gpio-controller to see if banked register paths bypass standard protectionAffected if GPIO banked register paths exist without access controls compared to standard GPIO resource paths
You are affected if your device uses any of the listed Qualcomm chipset models (Mdm9206, Mdm9607, Mdm9650, Sd 210/212/205, Sd 425, Sd 430) regardless of firmware version, as all versions of these chipsets contain the vulnerable GPIO register access implementation.
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 firmware updates for affected Snapdragon MDM9206, MDM9607, MDM9650, SD 210/212/205, SD 425, SD 430, SD 450, SD 625, SD 650/52, SD 835, and SDA660 devices to address this protection bypass.
- Consultation6.0 h
- Implementation10.0 h
- Testing8.0 h
- Review / QA5.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18293 — 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-18293 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