In nfc_enabled of nfc_main.cc, there is a possible out of bounds read due to an incorrect increment.

published 2020-12-15 5y ago modified 2026-06-17 4mo ago also EUVD-2020-19567

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

In nfc_enabled of nfc_main.cc, there is a possible out of bounds read due to an incorrect increment. This could lead to local information disclosure via firmware with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11Android ID: A-155234594

Patch / fix

links 1

source.android.com/security/bulletin/pixel/2020-12-01 advisory

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

CVSS scores

assigned by	version	score	vector
NVD	3.1	4.4	CVSS:3.1/AV:L/AC:L/PR:H/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-125 Out-of-bounds Read

References

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

Sources

CVE List CVE-2020-27043
NVD CVE-2020-27043

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.