CVE-2017-18655
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 · uneditedAn issue was discovered on Samsung mobile devices with M(6.0) and N(7.x) software. There is a stack-based buffer overflow with resultant memory corruption in a trustlet. The Samsung IDs are SVE-2017-8889, SVE-2017-8891, and SVE-2017-8892 (August 2017).
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 confidenceStack-based buffer overflow in a trustlet (secure trusted application) on Samsung mobile devices running Android M (6.0) and N (7.x), leading to memory corruption in a privileged execution environment.
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 data= 6.0= 7.0= 7.1.0= 7.1.1= 7.1.2CVSS 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.1/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.
-
Confirm device is a Samsung mobile deviceCheck the device manufacturer and model via Settings > About Phone > Device name, or run 'getprop ro.product.brand' and 'getprop ro.product.model' via ADB shellAffected if The device is not a Samsung brand
-
Verify Android version is 6.0 or 7.xGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if Android version is 6.0, 7.0, 7.1.0, 7.1.1, or 7.1.2
-
Check security patch levelGo to Settings > About Phone > Security patch level, or run 'getprop ro.build.version.security_patch' via ADB shellAffected if Security patch level is earlier than the Samsung SVE-2017-8889, SVE-2017-8891, or SVE-2017-8892 patch dates
A Samsung device running Android 6.0 through 7.1.2 with a security patch level predating the Samsung trustlet fixes is affected.
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 Samsung firmware updates corresponding to SVE-2017-8889, SVE-2017-8891, and SVE-2017-8892. Users should update their device to the latest Samsung-provided security patch level.
Upgrade to the latest available Android version supported by your device (Android 8.0+ or later) and ensure August 2017 or later security patch level is applied
- Check your Samsung device model and current Android/security patch level in Settings > About phone
- Apply the August 2017 Samsung security patch or later monthly security update via Settings > Software update > Download and install
- If updates are no longer available for your device model, consider upgrading to a newer device model that receives active security support
- Verify the security patch level has been updated in Settings > About phone after applying the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18655 — 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-18655 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