CVE-2020-0263
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 the Accessibility service, there is a possible permission bypass due to an unsafe PendingIntent. This could lead to local information disclosure with User execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11Android ID: A-154913130
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 confidenceIn the Android Accessibility service, an unsafe PendingIntent allows a permission bypass enabling local information disclosure. An attacker with an app installed on the device could exploit this without user interaction to access sensitive data that should be protected by the Accessibility service's 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= 11.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 Android version is 11.0Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADBAffected if The device is running Android 11.0 exactly. Other versions are not affected per the provided scope.
-
Identify enabled Accessibility servicesGo to Settings > Accessibility > Services, or inspect /data/system/accessibility_service_state.xml if accessible with rootAffected if Any Accessibility service is enabled on Android 11.0, creating the attack surface for the vulnerability.
-
Review apps with Accessibility permissionsGo to Settings > Apps > [select app] > Permissions > Accessibility, or run 'dumpsys package [app]' via ADB to check for android.permission.BIND_ACCESSIBILITY_SERVICEAffected if Any app other than trusted system services holds Accessibility permission on Android 11.0.
-
Check installed third-party apps for suspicious originsReview Settings > Apps > [app] > App info to identify sideloaded apps or those from unknown sourcesAffected if Sideloaded or non-Play Store apps with Accessibility permissions exist on the device.
-
Verify security patch levelGo to Settings > About Phone > Security patch level, or run 'getprop ro.build.version.security_patch' via ADBAffected if The installed Security Patch Level predates the fix for CVE-2020-0263 (patch date unknown from provided data).
A device is affected if it runs Android 11.0, has any Accessibility service enabled, and contains apps with Accessibility permissions, especially from third-party or sideloaded sources.
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 Android security patch level that addresses CVE-2020-0263. Until the vendor patch is available, consider disabling unnecessary Accessibility services, reviewing installed apps for legitimacy, and using enterprise mobility management to restrict app installations.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-0263 — 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-0263 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