{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-14855 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-14855 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-14855 is a medium-severity memory corruption vulnerability in n/a, published on 17 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-14855 and fix it if it is affected.\n\nWhat it is: CVE-2018-14855 is a medium-severity memory corruption vulnerability in n/a, published on 17 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-14855 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-14855/ (Markdown: https://insights.sbomify.com/CVE-2018-14855/index.md)","id":"CVE-2018-14855","markdown":"https://insights.sbomify.com/CVE-2018-14855/index.md","name":"CVE-2018-14855","record":{"aliases":["GHSA-5w63-xw96-85rr"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Samsung Galaxy S6","requires_auth":"none","summary":"A buffer overflow in the Wi-Fi driver allows attackers with chip access to cause invalid memory accesses, potentially leading to code execution on Samsung Galaxy S6 devices.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"galaxy_s6_firmware","vendor":"samsung"}],"cvss":{"score":6.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.0"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"Buffer overflow in dhd_bus_flow_ring_flush_response in drivers/net/wireless/bcmdhd4358/dhd_pcie.c in the bcmdhd4358 Wi-Fi driver on the Samsung Galaxy S6 allow an attacker (who has obtained code execution on the Wi-Fi chip) to cause the device driver to perform invalid memory accesses. The Samsung ID is SVE-2018-11785.","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":"Memory corruption in n/a","id":"CVE-2018-14855","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2018-14856"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2018-14854"},"products":["n/a"],"published":"2018-12-17","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2016-2566","kev_date_added":null,"published":"2017-04-13"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2018-14745","kev_date_added":null,"published":"2019-03-15"},{"cvss_score":6.3,"headline":"Memory corruption in n/a","id":"CVE-2018-14852","kev_date_added":null,"published":"2018-12-17"},{"cvss_score":6.3,"headline":"Memory corruption in n/a","id":"CVE-2018-14854","kev_date_added":null,"published":"2018-12-17"},{"cvss_score":6.3,"headline":"Memory corruption in n/a","id":"CVE-2018-14856","kev_date_added":null,"published":"2018-12-17"},{"cvss_score":4.3,"headline":"Null dereference in n/a","id":"CVE-2018-14853","kev_date_added":null,"published":"2018-12-17"}],"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 buffer overflow in the Wi-Fi driver allows attackers with chip access to cause invalid memory accesses, potentially leading to code execution on Samsung Galaxy S6 devices.","url":"https://insights.sbomify.com/CVE-2018-14855/"}