# CVE-2019-12762: Other in n/a

> Attackers can trigger touchscreen anomalies on Xiaomi Mi 5s Plus devices using specific radio signals, potentially disrupting user interaction.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-6qvh-cgqj-mqfm

## What is CVE-2019-12762?

CVE-2019-12762 is a medium-severity vulnerability in n/a, published on 6 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Xiaomi Mi 5s Plus devices allow attackers to trigger touchscreen anomalies via a radio signal between 198 kHz and 203 kHz, as demonstrated by a transmitter and antenna hidden just beneath the surface of a coffee-shop table, aka Ghost Touch.

## Which versions are affected by CVE-2019-12762?

It affects 8 products.


Products: Fujitsu Arrows Nx F05-F Firmware, Google Nexus 7 Firmware, Google Nexus 9 Firmware, Mi Mi 5s Plus Firmware, Samsung Galaxy S4 Firmware, Samsung Galaxy S6 Edge Firmware, Sharp Aquos Zeta Sh-04f Firmware, Sony Xperia Z4 Firmware.

## How do I fix CVE-2019-12762?

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

## Is CVE-2019-12762 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-12762 and fix it if it is affected.

What it is: CVE-2019-12762 is a medium-severity vulnerability in n/a, published on 6 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-12762 in the wild and no public exploit code.

Affected product: n/a. 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-2019-12762/ (Markdown: https://insights.sbomify.com/CVE-2019-12762/index.md)
```

## Sources

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

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