{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-15001 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-15001 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-15001 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-15001 and fix it if it is affected.\n\nWhat it is: CVE-2018-15001 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-15001 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-15001/ (Markdown: https://insights.sbomify.com/CVE-2018-15001/index.md)","id":"CVE-2018-15001","markdown":"https://insights.sbomify.com/CVE-2018-15001/index.md","name":"CVE-2018-15001","record":{"aliases":["GHSA-cm4p-7953-jqx5"],"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 device","requires_auth":"low_privilege","summary":"A malicious app can force the device to write sensitive system logs to external storage, potentially exposing private data to other apps with storage permissions.","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":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"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.bsptest (versionCode=1, versionName=1.0) containing an exported activity app component named com.vivo.bsptest.BSPTestActivity that allows any app co-located on the device to initiate the writing of the logcat log, bluetooth log, and kernel log to external storage. When logging is enabled, there is a notification in the status bar, so it is not completely transparent to the user. The user can cancel the logging, but it can be re-enabled since the app with a package name of com.vivo.bsptest cannot be disabled. The writing of these logs can be initiated by an app co-located on the device, although the READ_EXTERNAL_STORAGE permission is necessary to for an app to access the log files.","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-15001","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":"Information disclosure in n/a","id":"CVE-2018-15002"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2018-15000"},"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":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":"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 force the device to write sensitive system logs to external storage, potentially exposing private data to other apps with storage permissions.","url":"https://insights.sbomify.com/CVE-2018-15001/"}