CVE-2020-12754
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 LG mobile devices with Android OS 7.2, 8.0, 8.1, 9, and 10 software. A crafted application can obtain control of device input via the window system service. The LG ID is LVE-SMP-170011 (May 2020).
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 confidenceA crafted malicious application can obtain control of device input through the window system service on LG mobile devices running Android OS 7.2 through 10. This allows the malicious app to intercept or manipulate user input events at the system service level, effectively hijacking input control.
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.2= 8.0= 8.1= 9.0= 10.0CVSS 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
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/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.
-
Identify device manufacturer and modelCheck if the device is an LG mobile device by going to Settings > About Phone > Manufacturer or checking the device branding/boot screenAffected if The device is not an LG device - this vulnerability specifically affects LG mobile devices
-
Check Android OS versionGo to Settings > About Phone > Android version. Confirm the exact version number matches 7.2, 8.0, 8.1, 9.0, or 10.0Affected if The device runs Android 7.2, 8.0, 8.1, 9.0, or 10.0 - these are the affected versions per the CVE
-
Verify application installation sourceReview installed applications in Settings > Apps > See all apps. Check Settings > Security > Install unknown apps to see which apps are allowed to install other appsAffected if Applications from untrusted/non-play-store sources are installed, as the vulnerability requires a malicious application to be installed on the device
-
Inspect window system service statusUse ADB shell to check system_server permissions: dumpsys window. Review if any third-party apps hold SYSTEM_ALERT_WINDOW or accessibility permissions that could interact with the window system serviceAffected if Third-party apps have broad input/interaction permissions (SYSTEM_ALERT_WINDOW, accessibility services) that could potentially exploit the window system service vulnerability
You are affected if you are using an LG mobile device running Android 7.2, 8.0, 8.1, 9.0, or 10.0 AND you have installed applications from untrusted sources that could exploit the window system service.
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 vendor-supplied security patches from LG (LVE-SMP-170011) once released. Avoid installing applications from untrusted sources to prevent exploitation of this vulnerability.
- 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-2020-12754 — 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-2020-12754 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