CVE-2020-0387
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 · uneditedIn manifest files of the SmartSpace package, there is a possible tapjacking vector due to a missing permission check. This could lead to local escalation of privilege and account hijacking with no additional execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-156046804
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 a tapjacking vulnerability in Android's SmartSpace package where the manifest file lacks a proper permission check. Tapjacking allows a malicious overlay to intercept user touch events by placing a transparent or deceptive UI on top of legitimate app interfaces, potentially hijacking user actions and leading to account compromise.
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 dataall versionsCVSS 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 SmartSpace package on deviceRun 'pm list packages | grep smartspace' or check for packages with names containing 'smartspace' (e.g., com.android.launcher.smartspace, com.google.android.apps.search.quicksearchbox.smartspace)Affected if SmartSpace package exists on the device - this is the prerequisite for being affected
-
Locate the SmartSpace APKUse 'pm path <package_name>' to find the APK path, then access the APK file for manifest inspectionAffected if APK is accessible for analysis
-
Extract and inspect AndroidManifest.xmlUse apktool or similar tool to extract AndroidManifest.xml from the SmartSpace APK, then search for activity, service, or receiver tags that handle user interactionAffected if Manifest lacks android:filterTouchesWhenObscured='true' on UI components that handle touch events, or lacks implementation of onFilterTouchEventForSecurity callback in those components
-
Check for touch security protection in codeDecompile the APK and examine Java/Smali code for UI activity classes to see if onFilterTouchEventForSecurity method is implemented with proper logicAffected if No onFilterTouchEventForSecurity override exists in the touch-handling UI components, leaving touch events unprotected from overlay attacks
The environment is affected if SmartSpace package is installed AND its manifest lacks android:filterTouchesWhenObscured attribute AND its UI components do not implement onFilterTouchEventForSecurity protection.
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 dataAdd the appropriate permission check and security attributes in the SmartSpace manifest, such as android:filterTouchesWhenObscured or implementing onFilterTouchEventForSecurity in vulnerable UI components to prevent touch event interception.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-0387 — 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-0387 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