In callCallbackForRequest of ConnectivityService.java, there is a possible permission bypass due to a missing permission check.

published 2020-11-10 5y ago modified 2026-06-17 4mo ago also EUVD-2020-1955

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

In callCallbackForRequest of ConnectivityService.java, there is a possible permission bypass due to a missing permission check. This could lead to local information disclosure of the current SSID with User execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-9Android ID: A-161370134

Is CVE-2020-0454 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.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

usenix.org https://www.usenix.org/system/files/sec19-reardon.pdf referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Affected products

n/a Android

Classification

Weakness

CWE-862 Missing Authorization

References

usenix.org /system/files/sec19-reardon.pdf
exploit, third-party-advisory
source.android.com /security/bulletin/2020-11-01
vendor-advisory
usenix.org /conference/usenixsecurity19/presentation/reardon
third-party-advisory

Sources

CVE List CVE-2020-0454
NVD CVE-2020-0454

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.