The frame touch module does not make validity judgments on parameter lengths when processing specific parameters,which caused out of the bo…

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

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

The frame touch module does not make validity judgments on parameter lengths when processing specific parameters,which caused out of the boundary when memory access.The vulnerability eventually leads to a local DOS on the device.

Patch / fix

fixed in 1

vivo The frame touch module PD1962_1.7.6, PD1965EF_EX_EU_4.4.0, PD1968F_EX_1.10.1, PD1981_1.5.0, PD2001F_EX_1.6.0, PD2006F_EX_1.6.2, PD2012_1.4.0

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

CVSS scores

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

Affected products

vivo The frame touch module

Classification

Weakness

CWE-125 Out-of-bounds Read

References

vivo.com /en/support/security-advisory-detail?id=2
vendor-advisory

Sources

CVE List CVE-2020-12485
NVD CVE-2020-12485

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.