{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-6899 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2017-6899 is a medium-severity vulnerability in n/a, published on 16 Jun 2017. 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-2017-6899 and fix it if it is affected.\n\nWhat it is: CVE-2017-6899 is a medium-severity vulnerability in n/a, published on 16 Jun 2017. 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-2017-6899 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-6899/ (Markdown: https://insights.sbomify.com/CVE-2017-6899/index.md)","id":"CVE-2017-6899","markdown":"https://insights.sbomify.com/CVE-2017-6899/index.md","name":"CVE-2017-6899","record":{"aliases":["GHSA-gf68-qxhp-mhcf"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Android MSM kernel","requires_auth":"none","summary":"Attackers can crash Android MSM devices by writing to a debug interface, causing a denial of service via null pointer dereference.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"lineageos","vendor":"lineageos"}],"cvss":{"score":6.2,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"The msm_bus_dbg_update_request_write function in drivers/platform/msm/msm_bus/msm_bus_dbg.c in android_kernel_huawei_msm8916 through 2017-06-16 in LineageOS, and possibly other kernels for MSM devices, allows attackers to cause a denial of service (NULL pointer dereference and device crash) via a crafted /sys/kernel/debug/msm-bus-dbg/client-data/update-request write request.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Null dereference in n/a","id":"CVE-2017-6899","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Command injection in n/a","id":"CVE-2017-6900"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2017-6896"},"products":["n/a"],"published":"2017-06-16","related":[{"cvss_score":6.8,"headline":"Privilege escalation in LineageOS","id":"CVE-2019-1010221","kev_date_added":null,"published":"2019-07-23"}],"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 Android MSM devices by writing to a debug interface, causing a denial of service via null pointer dereference.","url":"https://insights.sbomify.com/CVE-2017-6899/"}