CVE-2018-14981
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 · uneditedCertain LG devices based on Android 6.0 through 8.1 have incorrect access control for SystemUI application intents. The LG ID is LVE-SMP-180005.
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 confidenceLG devices running Android 6.0 through 8.1 have incorrect access control for SystemUI application intents, allowing untrusted applications to send privileged intents to the SystemUI component. This could enable a malicious application to interact with or manipulate system UI functionality without proper permissions.
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= 6.0.1= 7.0= 7.1= 7.2= 8.0= 8.1CVSS 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.
-
Confirm device manufacturer is LGGo to Settings > About Phone > Manufacturer or use 'getprop ro.product.manufacturer' via ADBAffected if Device is not manufactured by LG, then this specific vulnerability does not apply
-
Check Android versionGo to Settings > About Phone > Android version or use 'getprop ro.build.version.release' via ADBAffected if Version is 6.0, 6.0.1, 7.0, 7.1, 7.2, 8.0, or 8.1 - other versions are not affected by this CVE
-
Verify LG security patch statusGo to Settings > About Phone > Software info > Security patch level or use 'getprop ro.build.version.security_patch' via ADBAffected if Security patch level is earlier than the LVE-SMP-180005 patch date, meaning the vendor fix has not been applied
-
Audit installed applicationsReview Settings > Apps > Downloaded for any untrusted or suspicious applications that were installed from unknown sourcesAffected if A malicious application is installed that could exploit the SystemUI intent vulnerability
User is affected if they have an LG device running Android 6.0 through 8.1 that has not received the LVE-SMP-180005 vendor security patch.
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 LG vendor security patches (LVE-SMP-180005) to affected devices. Until patches are available, consider network isolation or restricting app installation to trusted sources only, as exploitation requires a malicious application to be installed.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-14981 — 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-14981 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