CVE-2017-18133
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 and Snapdragon Wear MDM9206, MDM9607, MDM9650, SD 210/SD 212/SD 205, SD 835, an out of bound access for ebi channel array can potentially occur.
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 confidenceAn out-of-bounds memory access vulnerability in the ebi (likely External Bus Interface) channel array exists in Qualcomm Snapdragon chipsets (MDM9206, MDM9607, MDM9650, SD 210/SD 212/SD 205, SD 835) running Android versions before the 2018-04-05 security patch level. This is a memory corruption flaw at the firmware/hardware abstraction layer that could allow code execution at elevated privileges.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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.
-
Check Android security patch levelGo to Settings > About Phone > Android security patch level, or run 'getprop ro.build.version.security_patch' via adb shellAffected if Security patch level is earlier than 2018-04-05 (e.g., 2018-03-05, 2018-02-05, or older)
-
Identify the chipset modelRun 'getprop ro.hardware' or 'getprop ro.board.platform' via adb shell, or check via device info in Settings > About PhoneAffected if Chipset matches one of: MDM9206, MDM9607, MDM9650, SD 210, SD 212, SD 205, or SD 835
Device is affected if it uses any of the listed Qualcomm chipsets AND has not received the 2018-04-05 or later Android security patch level.
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.
dbcve · scopedApply the Android security patch level 2018-04-05 or later via OEM firmware updates; for affected devices no longer receiving updates, consider network segmentation or device replacement.
Android security patch level 2018-04-05 or later (or device vendor firmware incorporating this patch)
- Check current Android security patch level on the device (Settings > About Phone > Security patch level)
- Update the device to the Android security patch level 2018-04-05 or later
- This is typically achieved by applying the monthly Android security update from the device manufacturer
- If the device manufacturer no longer provides updates, consider upgrading to a device that still receives security patches
- For embedded/IoT devices using these Qualcomm modems, contact the device vendor for firmware updates that include the April 2018 security patch
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation2.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,672.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18133 — 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-18133 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