CVE-2018-15002
Last modified
CVE-2018-15002 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.30% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Vivo | V7 Firmware | 7.1.2 |
References
- https://www.kryptowire.com/portal/android-firmware-defcon-2018/Third Party Advisory
- https://www.kryptowire.com/portal/android-firmware-defcon-2018/Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2018-15002?
How severe is CVE-2018-15002?
How do I fix CVE-2018-15002?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2018
- CVE-2018-14996The Oppo F5 Android device with a build fingerprint of OPPO/…
- CVE-2018-14997The Leagoo P1 Android device with a build fingerprint of sp7…
- CVE-2018-14998The Leagoo P1 Android device with a build fingerprint of sp7…
- CVE-2018-14999The Leagoo P1 device with a build fingerprint of sp7731c_1h1…
- CVE-2018-15000The Vivo V7 Android device with a build fingerprint of vivo/…
- CVE-2018-15001The Vivo V7 Android device with a build fingerprint of vivo/…
- CVE-2018-15003The Coolpad Defiant (Coolpad/cp3632a/cp3632a:7.1.1/NMF26F/09…
- CVE-2018-15004The Coolpad Canvas device with a build fingerprint of Coolpa…
- CVE-2018-15005The ZTE ZMAX Champ Android device with a build fingerprint o…
- CVE-2018-15006The ZTE ZMAX Champ Android device with a build fingerprint o…
- CVE-2018-15007The Sky Elite 6.0L+ Android device with a build fingerprint …
- CVE-2018-1501IBM Security Guardium 10.5, 10.6, and 11.0 could allow an un…7.5
Are you affected by CVE-2018-15002?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
