CVE-2018-9142
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 · uneditedOn Samsung mobile devices with N(7.x) software, attackers can install an arbitrary APK in the Secure Folder SD Card area because of faulty validation of a package signature and package name, aka SVE-2017-10932.
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 confidenceOn Samsung mobile devices running Android N (7.x), a vulnerability in the Secure Folder feature allowed attackers to install arbitrary APK files in the Secure Folder SD Card area due to insufficient validation of package signatures and package names. This bypassed the intended security boundaries of the Secure Folder, which is designed to isolate sensitive applications and data.
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= 7.0= 7.1= 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
- Local
- Complexity
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:H/PR:N/UI:R/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.
-
Verify Android version is 7.xGo to Settings > About Phone > Android version. Confirm the version is exactly 7.0, 7.1, 7.1.1, or 7.1.2Affected if Android version is 7.0, 7.1, 7.1.1, or 7.1.2 on a Samsung device
-
Confirm device is SamsungCheck the device manufacturer. Go to Settings > About Phone > Device name or manufacturer. Samsung devices are affected; other manufacturers are not in scope for this CVEAffected if Device is made by Samsung and runs Android 7.x versions listed above
-
Check if Secure Folder is presentLook for Secure Folder app on the device. On Samsung devices running Android N, Secure Folder is typically found in Settings > Biometrics and security > Secure Folder, or search for 'Secure Folder' in the app drawerAffected if Secure Folder feature exists and is accessible on the device (vulnerability requires Secure Folder to be present)
-
Verify Samsung security patch levelGo to Settings > About Phone > Security patch level. Check if the installed security updates are dated after the SVE-2017-10932 patch release. The patch was released by Samsung to address this specific vulnerabilityAffected if Security patch level is earlier than the SVE-2017-10932 fix or the device has not received Samsung's security update for this vulnerability
A Samsung device is affected if it runs Android 7.0-7.1.2, has the Secure Folder feature, and lacks the vendor security patch addressing SVE-2017-10932
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 vendor security patch released by Samsung for this vulnerability (SVE-2017-10932). Users should ensure their devices are running the latest available Samsung security updates.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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 $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-9142 — 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-2018-9142 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