An information disclosure vulnerability in the Framework APIs could enable a local malicious application to bypass operating system protect…

published 2017-02-08 9y ago modified 2026-06-17 4mo ago also EUVD-2017-0775

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

An information disclosure vulnerability in the Framework APIs could enable a local malicious application to bypass operating system protections that isolate application data from other applications. This issue is rated as High because it could be used to gain access to data that the application does not have access to. Product: Android. Versions: 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1. Android ID: A-32555637.

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

CVSS scores

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

Affected products

Google Inc. Android

Classification

Weakness

CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

source.android.com /security/bulletin/2017-02-01.html
vendor-advisory
securityfocus.com /bid/96096
vdb-entry, third-party-advisory
securitytracker.com /id/1037798
vdb-entry

Sources

CVE List CVE-2017-0421
NVD CVE-2017-0421

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.