In onCreate of RequestPermissionActivity.java, there is a possible tapjacking vector due to an insecure default value.

published 2020-09-17 6y ago modified 2026-06-17 4mo ago also EUVD-2020-1889

cvss: 5.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 32%
public exploits: 0; none known

In onCreate of RequestPermissionActivity.java, there is a possible tapjacking vector due to an insecure default value. This could lead to local escalation of privilege allowing an attacker to set Bluetooth discoverability with User execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-8.0 Android-8.1 Android-9 Android-10 Android-11Android ID: A-155650356

Patch / fix

links 1

source.android.com/security/bulletin/2020-09-01 advisory

Is CVE-2020-0386 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.39% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	5.5	CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
NVD	2.0	4.3	AV:N/AC:M/Au:N/C:N/I:P/A:N

Affected products

n/a Android

Classification

Weakness

CWE-1021 Improper Restriction of Rendered UI Layers or Frames
CWE-1188 Initialization of a Resource with an Insecure Default

References

source.android.com /security/bulletin/2020-09-01
patch, vendor-advisory

Sources

CVE List CVE-2020-0386
NVD CVE-2020-0386

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.