{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-15000 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-15000 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-15000 is a medium-severity vulnerability in n/a, published on 25 Apr 2019. 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-15000 and fix it if it is affected.\n\nWhat it is: CVE-2018-15000 is a medium-severity vulnerability in n/a, published on 25 Apr 2019. 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-15000 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-15000/ (Markdown: https://insights.sbomify.com/CVE-2018-15000/index.md)","id":"CVE-2018-15000","markdown":"https://insights.sbomify.com/CVE-2018-15000/index.md","name":"CVE-2018-15000","record":{"aliases":["GHSA-r85j-p62h-x482"],"analysis":{"component_type":"mobile_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Vivo Android app","requires_auth":"low_privilege","summary":"A malicious app can silently record the screen for 60 minutes by exploiting a service in the Vivo SmartShot app, bypassing user notification visibility.","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":6.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.0"},"cwes":[],"description":"The Vivo V7 Android device with a build fingerprint of vivo/1718/1718:7.1.2/N2G47H/compil11021857:user/release-keys contains a platform app with a package name of com.vivo.smartshot (versionCode=1, versionName=3.0.0). This app contains an exported service named com.vivo.smartshot.ui.service.ScreenRecordService that will record the screen for 60 minutes and write the mp4 file to a location of the user's choosing. Normally, a recording notification will be visible to the user, but we discovered an approach to make it mostly transparent to the user by quickly removing a notification and floating icon. The user can see a floating icon and notification appear and disappear quickly due to quickly stopping and restarting the service with different parameters that do not interfere with the ongoing screen recording. The screen recording lasts for 60 minutes and can be written directly to the attacking app's private directory.","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-15000","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2018"},"n_packages":0,"n_references":3,"next":{"headline":"Information disclosure in n/a","id":"CVE-2018-15001"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2018-14999"},"products":["n/a"],"published":"2019-04-25","related":[{"cvss_score":5.5,"headline":"Information disclosure in n/a","id":"CVE-2018-15001","kev_date_added":null,"published":"2018-12-28"},{"cvss_score":4.7,"headline":"Information disclosure in n/a","id":"CVE-2018-15002","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":"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 silently record the screen for 60 minutes by exploiting a service in the Vivo SmartShot app, bypassing user notification visibility.","url":"https://insights.sbomify.com/CVE-2018-15000/"}