In multiple settings screens, there are possible tapjacking attacks due to an insecure default value.

published 2020-10-14 6y ago modified 2026-06-17 4mo ago also EUVD-2020-1918

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

In multiple settings screens, there are possible tapjacking attacks due to an insecure default value. This could lead to local escalation of privilege and permissions with no additional execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-9 Android-10 Android-11 Android-8.0 Android-8.1Android ID: A-155288585

Patch / fix

links 1

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

Is CVE-2020-0416 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

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

CVSS scores

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

Affected products

n/a Android

Classification

Weakness

CWE-1188 Initialization of a Resource with an Insecure Default

References

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

Sources

CVE List CVE-2020-0416
NVD CVE-2020-0416

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.