CVE-2017-18128
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 · uneditedIn Android before security patch level 2018-04-05 on Qualcomm Snapdragon Mobile SD 845, SD 850, improper access control while configuring MPU protecting error correction registers may potentially lead to exposure of related secured data.
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 confidenceThis is a hardware-level access control vulnerability in Qualcomm Snapdragon SD 845 and SD 850 chipsets. The Memory Protection Unit (MPU) configuration for error correction registers was improperly set up, potentially allowing unauthorized access to secured data stored in those registers. The vulnerability was addressed in the Android security patch level dated 2018-04-05.
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 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/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 your chipset modelCheck the device specifications or system-on-chip information to confirm whether the system uses a Qualcomm Snapdragon SD 845 or SD 850 chipset. This is typically listed in the device specs or can be obtained via system information utilities.Affected if The device does NOT have a Snapdragon SD 845 or SD 850 chipset, then this specific CVE does not apply.
-
Determine the Android security patch levelOn Android devices, go to Settings > About Phone > Software Information and look for the 'Android security patch level' field. Alternatively, use the command 'getprop ro.build.version.security_patch' via ADB shell to retrieve the patch level.Affected if The security patch level is earlier than 2018-04-05, indicating the vulnerability has not been addressed.
-
Check firmware version for embedded systemsFor embedded or IoT devices using these Snapdragon variants, consult the device firmware documentation or use manufacturer-provided tools to query the firmware version. Contact the device manufacturer if this information is not accessible.Affected if The firmware is all versions and has not been updated by the manufacturer to include the 2018-04-05 fix.
If the device contains a Qualcomm Snapdragon SD 845 or SD 850 chipset and the Android security patch level is earlier than 2018-04-05 (or the firmware has not been patched), the environment is affected by CVE-2017-18128.
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 the Android security patch level 2018-04-05 or later to affected devices. For embedded systems using these Snapdragon variants, obtain and deploy the corresponding firmware update from Qualcomm.
- Consultation8.0 h
- Implementation12.0 h
- Testing6.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 $8,608.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18128 — 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-18128 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