In getVSCoverage of CmapCoverage.cpp, there is a possible out of bounds read due to an incorrect bounds check.

published 2018-04-04 8y ago modified 2026-06-17 4mo ago also EUVD-2017-4792

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

In getVSCoverage of CmapCoverage.cpp, there is a possible out of bounds read due to an incorrect bounds check. This could lead to local information disclosure with no additional privileges needed. User interaction is needed for exploitation. Product: Android. Versions: 8.0, 8.1. Android ID: A-70808908.

Is CVE-2017-13275 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.15% chance of exploitation in the next 30 days, higher than 4% 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	1.9	AV:L/AC:M/Au:N/C:P/I:N/A:N

Affected products

Google Inc. Android

Classification

Weakness

CWE-125 Out-of-bounds Read

References

source.android.com /security/bulletin/2018-04-01
vendor-advisory

Sources

CVE List CVE-2017-13275
NVD CVE-2017-13275

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.