{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-5351 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-5351 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-5351 is a high-severity denial of service vulnerability in n/a, published on 12 Jan 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-5351 and fix it if it is affected.\n\nWhat it is: CVE-2017-5351 is a high-severity denial of service vulnerability in n/a, published on 12 Jan 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-5351 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-5351/ (Markdown: https://insights.sbomify.com/CVE-2017-5351/index.md)","id":"CVE-2017-5351","markdown":"https://insights.sbomify.com/CVE-2017-5351/index.md","name":"CVE-2017-5351","record":{"aliases":["GHSA-5gf7-6q77-r2pv"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Samsung Note devices","requires_auth":"none","summary":"Attackers can crash Samsung Note devices by creating an excessive number of active VR service threads, causing a denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"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:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"Samsung Note devices with KK(4.4), L(5.0/5.1), and M(6.0) software allow attackers to crash the system by creating an arbitrarily large number of active VR service threads. The Samsung ID is SVE-2016-7650.","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":"Denial of service in n/a","id":"CVE-2017-5351","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Denial of service in n/a","id":"CVE-2017-5356"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2017-5350"},"products":["n/a"],"published":"2017-01-12","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-08-05","vendors":["n/a"]},"summary":"Attackers can crash Samsung Note devices by creating an excessive number of active VR service threads, causing a denial of service.","url":"https://insights.sbomify.com/CVE-2017-5351/"}