CVE-2017-18662
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. Data outside of the rkp log buffer boundary is read, causing an information leak. The Samsung ID is SVE-2017-9109 (July 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 confidenceThis is an information disclosure vulnerability in Samsung mobile devices running Android M (6.0) and N (7.x). The vulnerability allows reading data outside the boundary of the rkp (Real-time Kernel Protection) log buffer, potentially exposing sensitive kernel memory contents. This out-of-bounds read has a CVSS score of 7.5 (HIGH).
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
- None
- Availability
- None
CVSS:3.1/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.
-
Confirm device is a Samsung mobile deviceCheck the device manufacturer via Settings > About Phone > Manufacturer or by running 'getprop ro.product.manufacturer' in ADB shellAffected if The device is not manufactured by Samsung, the vulnerability does not apply
-
Check the Android versionNavigate to Settings > About Phone > Android version or run 'getprop ro.build.version.release' in ADB shellAffected if The version is exactly 6.0, 7.0, 7.1.0, 7.1.1, or 7.1.2 - other versions are not affected
-
Verify if rkp (Real-time Kernel Protection) logging is enabledInspect the kernel configuration or rkp-related system properties via 'getprop | grep rkp' in ADB shell - the vulnerability exists in the rkp log buffer componentAffected if The rkp feature is present and its log buffer is accessible - the out-of-bounds read can occur
-
Check the installed security patch levelGo to Settings > About Phone > Security patch level or run 'getprop ro.build.version.security_patch' in ADB shellAffected if The patch level is earlier than July 2017 (before SVE-2017-9109 was applied)
A Samsung device running Android 6.0 through 7.1.2 with rkp logging enabled and a security patch level before July 2017 is affected by this out-of-bounds read vulnerability in the rkp log buffer.
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 Samsung security update SVE-2017-9109 (July 2017 patch) to affected devices. Users should update their Samsung mobile devices to the latest available security patch level.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.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,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18662 — 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-18662 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