# CVE-2020-12485: Denial of service in The frame touch module

> A local denial of service vulnerability in the vivo frame touch module allows attackers to crash the device via out-of-bounds memory access.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Nov 2020
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-975g-xrmq-9xmj

## What is CVE-2020-12485?

CVE-2020-12485 is a medium-severity denial of service vulnerability in vivo The frame touch module, published on 10 Nov 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2020-12485?

It affects 1 product.


Products: Vivo Frame Touch Module.

## How do I fix CVE-2020-12485?

No fix has been published for CVE-2020-12485 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-12485 being exploited?

There is no known exploitation of CVE-2020-12485 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-12485 and fix it if it is affected.

What it is: CVE-2020-12485 is a medium-severity denial of service vulnerability in vivo The frame touch module, published on 10 Nov 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-12485 in the wild and no public exploit code.

Affected product: vivo The frame touch module. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-12485/ (Markdown: https://insights.sbomify.com/CVE-2020-12485/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-12485
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-12485
- OSV: https://osv.dev/vulnerability/CVE-2020-12485

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-12485/
Summaries are generated and may contain mistakes; the official description above is the record.