{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-15002 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-15002 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2018-15002 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2018-15002 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2018-15002/ (Markdown: https://insights.sbomify.com/CVE-2018-15002/index.md)","id":"CVE-2018-15002","markdown":"https://insights.sbomify.com/CVE-2018-15002/index.md","name":"CVE-2018-15002","record":{"aliases":["GHSA-xq88-7x7g-c8p2"],"analysis":{"component_type":"mobile_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Qualcomm modem test app","requires_auth":"low_privilege","summary":"A malicious app can set system properties to log user touch coordinates, enabling keylogger-style data theft on Vivo devices.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"v7_firmware","vendor":"vivo"}],"cvss":{"score":4.7,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2018-15002","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Missing authorization in n/a","id":"CVE-2018-15003"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2018-15001"},"products":["n/a"],"published":"2018-12-28","related":[{"cvss_score":6.3,"headline":"Information disclosure in n/a","id":"CVE-2018-15000","kev_date_added":null,"published":"2019-04-25"},{"cvss_score":5.5,"headline":"Information disclosure in n/a","id":"CVE-2018-15001","kev_date_added":null,"published":"2018-12-28"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"A malicious app can set system properties to log user touch coordinates, enabling keylogger-style data theft on Vivo devices.","url":"https://insights.sbomify.com/CVE-2018-15002/"}