CVE-2017-18282
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 · uneditedNon-secure SW can cause SDCC to generate secure bus accesses, which may expose RPM access 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 · moderate confidenceNon-secure software can trigger the SDCC (Secure Digital Card Controller) to generate secure bus accesses, bypassing security boundaries and exposing RPM (Resource Power Manager) access on affected Snapdragon chipsets.
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 affected Qualcomm chipset usageInventory your devices to determine if any utilize the following Qualcomm chipsets: Mdm9206, Mdm9607, Mdm9650, Sd210, Sd212, Sd205, Sd425, or Sd430. Check device specifications, modem firmware identifiers, or chipset documentation.Affected if Any device in the environment uses one of the listed Qualcomm chipsets
-
Check SDCC firmware versionFor devices with affected chipsets, retrieve the SDCC (Secure Digital Card Controller) firmware version through manufacturer diagnostic tools, debug interfaces, or modem AT command interfaces if available.Affected if The SDCC firmware version is any version (all versions are affected according to the advisory)
-
Verify RPM access control configurationInspect the RPM (Resource Power Manager) security configuration on the affected chipset. Check if the secure bus access controls are enforced by examining secure boot settings, TrustZone configuration, or RPM policy files.Affected if RPM access controls are not properly configured to prevent non-secure software from generating secure bus accesses
-
Review chipset vendor documentationConsult Qualcomm or device manufacturer documentation to confirm the specific chipset model and firmware baseline. Cross-reference the chipset ID with the affected product list.Affected if The confirmed chipset matches Mdm9206, Mdm9607, Mdm9650, Sd210, Sd212, Sd205, Sd425, or Sd430
A user is affected if their device or environment contains any of the listed Qualcomm chipsets (Mdm9206, Mdm9607, Mdm9650, Sd210, Sd212, Sd205, Sd425, Sd430) running any firmware version.
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 dataThis hardware/firmware vulnerability requires firmware patches from Qualcomm and subsequent device manufacturer updates; organizations should inventory affected devices and apply vendor updates when available.
- Consultation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18282 — 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-18282 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