# CVE-2018-15002: Information disclosure in n/a

> A malicious app can set system properties to log user touch coordinates, enabling keylogger-style data theft on Vivo devices.

- **Severity:** Medium 4.7 (`CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xq88-7x7g-c8p2

## What is CVE-2018-15002?

CVE-2018-15002 is a medium-severity vulnerability in n/a, published on 28 Dec 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Vivo V7 device with a build fingerprint of vivo/1718/1718:7.1.2/N2G47H/compil11021857:user/release-keys allows any app co-located on the device to set system properties as the com.android.phone user. The com.qualcomm.qti.modemtestmode app (versionCode=25, versionName=7.1.2) that contains an exported service named com.qualcomm.qti.modemtestmode.MbnTestService that allows any app co-located on the device to provide key-value pairs to set certain system properties. Notably, system properties with the persist.* prefix can be set which will survive a reboot. On the Vivo V7 device, when the persist.sys.input.log property is set to have a value of yes, the user's screen touches be written to the logcat log by the InputDispatcher for all apps. The system-wide logcat log can be obtained from external storage via a different known vulnerability on the device. The READ_EXTERNAL_STORAGE permission is necessary to access the log files containing the user's touch coordinates. With some effort, the user's touch coordinates can be mapped to key presses on a keyboard.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2018-15002?

It affects 1 product.


Products: Vivo V7 Firmware.

## How do I fix CVE-2018-15002?

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

## Is CVE-2018-15002 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-15000](https://insights.sbomify.com/CVE-2018-15000/): Information disclosure in n/a (medium 6.3)
- [CVE-2018-15001](https://insights.sbomify.com/CVE-2018-15001/): Information disclosure in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-15002 and fix it if it is affected.

What it is: CVE-2018-15002 is a medium-severity vulnerability in n/a, published on 28 Dec 2018. 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-2018-15002 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-2018-15002/ (Markdown: https://insights.sbomify.com/CVE-2018-15002/index.md)
```

## Sources

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

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