{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-14318 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-14318 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-14318 is a high-severity memory corruption vulnerability in Samsung Galaxy S8, published on 25 Sep 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2018-14318 and fix it if it is affected.\n\nWhat it is: CVE-2018-14318 is a high-severity memory corruption vulnerability in Samsung Galaxy S8, published on 25 Sep 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2018-14318 in the wild and no public exploit code.\n\nAffected product: Samsung Galaxy S8. 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-14318/ (Markdown: https://insights.sbomify.com/CVE-2018-14318/index.md)","id":"CVE-2018-14318","markdown":"https://insights.sbomify.com/CVE-2018-14318/index.md","name":"CVE-2018-14318","record":{"aliases":["GHSA-qgmj-q7c2-vqvv"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Samsung Galaxy S8","requires_auth":"none","summary":"Remote attackers can execute arbitrary code on Samsung Galaxy S8 devices via a stack-based buffer overflow in IPCP header handling.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"zdi","cpe":[{"product":"galaxy_s8_firmware","vendor":"samsung"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"},{"id":"CWE-121","name":"Stack-based Buffer Overflow"}],"description":"This vulnerability allows remote attackers to execute arbitrary code on vulnerable installations of Samsung Galaxy S8 G950FXXU1AQL5. User interaction is required to exploit this vulnerability in that the target must have their cellular radios enabled. The specific flaw exists within the handling of IPCP headers. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length, stack-based buffer. An attacker can leverage this vulnerability to execute code under the context of the baseband processor. Was ZDI-CAN-5368.","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 Samsung Galaxy S8","id":"CVE-2018-14318","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 PoDoFo PoDoFo","id":"CVE-2018-14320"},"packages":[],"prev":{"headline":"Memory corruption in Foxit Reader","id":"CVE-2018-14317"},"products":["Samsung Galaxy S8"],"published":"2018-09-25","related":[],"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":["Samsung"]},"summary":"Remote attackers can execute arbitrary code on Samsung Galaxy S8 devices via a stack-based buffer overflow in IPCP header handling.","url":"https://insights.sbomify.com/CVE-2018-14318/"}