{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-14459 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-14459 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-14459 is a high-severity memory corruption vulnerability in n/a, published on 20 Jul 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-14459 and fix it if it is affected.\n\nWhat it is: CVE-2018-14459 is a high-severity memory corruption vulnerability in n/a, published on 20 Jul 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-14459 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-14459/ (Markdown: https://insights.sbomify.com/CVE-2018-14459/index.md)","id":"CVE-2018-14459","markdown":"https://insights.sbomify.com/CVE-2018-14459/index.md","name":"CVE-2018-14459","record":{"aliases":["DEBIAN-CVE-2018-14459","GHSA-hgqw-xx48-9ppq","UBUNTU-CVE-2018-14459"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"libgig library","requires_auth":"none","summary":"An out-of-bounds write in libgig allows attackers to potentially execute arbitrary code or cause a denial of service via crafted input.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"libgig","vendor":"linuxsampler"}],"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-787","name":"Out-of-bounds Write"}],"description":"An issue was discovered in libgig 4.1.0. There is an out-of-bounds write in pData[0] access in the function store16 in helper.h.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Memory corruption in n/a","id":"CVE-2018-14459","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-14460"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2018-14458"},"products":["n/a"],"published":"2018-07-20","related":[{"cvss_score":9.8,"headline":"Denial of service in n/a","id":"CVE-2018-18197","kev_date_added":null,"published":"2018-10-09"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2021-32294","kev_date_added":null,"published":"2021-09-20"},{"cvss_score":8.8,"headline":"Denial of service in n/a","id":"CVE-2018-18193","kev_date_added":null,"published":"2018-10-09"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2018-18194","kev_date_added":null,"published":"2018-10-09"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2018-18196","kev_date_added":null,"published":"2018-10-09"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2018-14449","kev_date_added":null,"published":"2018-07-20"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2018-14450","kev_date_added":null,"published":"2018-07-20"}],"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":"An out-of-bounds write in libgig allows attackers to potentially execute arbitrary code or cause a denial of service via crafted input.","url":"https://insights.sbomify.com/CVE-2018-14459/"}