{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-7978 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-7978 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-7978 is a high-severity vulnerability in n/a, published on 19 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-7978 and fix it if it is affected.\n\nWhat it is: CVE-2017-7978 is a high-severity vulnerability in n/a, published on 19 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-7978 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-2017-7978/ (Markdown: https://insights.sbomify.com/CVE-2017-7978/index.md)","id":"CVE-2017-7978","markdown":"https://insights.sbomify.com/CVE-2017-7978/index.md","name":"CVE-2017-7978","record":{"aliases":["GHSA-28v6-fvvw-2v6h"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Samsung Android OS","requires_auth":"none","summary":"Attackers can read sensitive information from world-readable log files on Samsung Android devices after an unexpected reboot.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"samsung_mobile","vendor":"samsung"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Samsung Android devices with L(5.0/5.1), M(6.0), and N(7.x) software allow attackers to obtain sensitive information by reading a world-readable log file after an unexpected reboot. The Samsung ID is SVE-2017-8290.","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-2017-7978","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in n/a","id":"CVE-2017-7979"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2017-7977"},"products":["n/a"],"published":"2017-04-19","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2018-9139","kev_date_added":null,"published":"2018-03-30"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2018-9143","kev_date_added":null,"published":"2018-03-30"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2017-5538","kev_date_added":null,"published":"2017-03-23"},{"cvss_score":9.8,"headline":"Denial of service in n/a","id":"CVE-2016-9965","kev_date_added":null,"published":"2016-12-16"},{"cvss_score":9.8,"headline":"Denial of service in n/a","id":"CVE-2016-9966","kev_date_added":null,"published":"2016-12-16"},{"cvss_score":9.8,"headline":"Denial of service in n/a","id":"CVE-2016-9967","kev_date_added":null,"published":"2016-12-16"},{"cvss_score":8.4,"headline":"Memory corruption in n/a","id":"CVE-2017-18020","kev_date_added":null,"published":"2018-01-04"}],"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-09-17","vendors":["n/a"]},"summary":"Attackers can read sensitive information from world-readable log files on Samsung Android devices after an unexpected reboot.","url":"https://insights.sbomify.com/CVE-2017-7978/"}