CVE-2017-18677
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. Because of an unprotected Intent, an attacker can reset the configuration of certain applications. The Samsung ID is SVE-2016-7142 (April 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 · high confidenceThis vulnerability in Samsung mobile devices running Android M (6.0) and N (7.x) allows an attacker to reset application configurations through an unprotected Intent. The Intent broadcast is not properly protected with permissions, enabling any application or malicious actor to send that Intent and manipulate settings of certain apps.
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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 device manufacturerCheck the device settings to confirm the manufacturer is Samsung. Look in Settings > About Phone > Manufacturer or Brand.Affected if Device is not a Samsung mobile device - this CVE specifically affects Samsung devices
-
Check Android version numberNavigate to Settings > About Phone > Android version (or Settings > System > About Phone > Android version). Record the full version number displayed.Affected if Version is not 6.0, 7.0, 7.1.0, 7.1.1, or 7.1.2 - only these exact versions are affected per the CVE
-
Verify exact version matchCompare your installed Android version against the affected list: 6.0, 7.0, 7.1.0, 7.1.1, 7.1.2. This is an exact version match (not a range).Affected if Your version does not exactly match one of: 6.0, 7.0, 7.1.0, 7.1.1, or 7.1.2
-
Confirm no security patch appliedCheck Settings > About Phone > Security patch level. If the device shows a security patch date, verify it is earlier than Samsung's fix release for this CVE.Affected if No Samsung security patch for CVE-2017-18677 has been applied (patch date unknown or pre-fix)
If the device is a Samsung mobile device running exactly Android 6.0, 7.0, 7.1.0, 7.1.1, or 7.1.2 and has not received the Samsung security fix for this vulnerability, the device 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.
From vendor dataSamsung should release a security update that properly protects the affected Intent with appropriate permission checks. Enterprises with affected devices should apply available Samsung security patches and consider using MDM solutions to enforce configuration policies as a defense-in-depth measure.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18677 — 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-18677 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