{"answers":{"affected":"It affects 2 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-0776 exists.","fix":"No fix has been published for CVE-2018-0776 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-0776 is a high-severity memory corruption vulnerability in Microsoft Chakracore, published on 4 Jan 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-0776 and fix it if it is affected.\n\nWhat it is: CVE-2018-0776 is a high-severity memory corruption vulnerability in Microsoft Chakracore, published on 4 Jan 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-0776 exists.\n\nAffected product: Microsoft Chakracore. 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-0776/ (Markdown: https://insights.sbomify.com/CVE-2018-0776/index.md)","id":"CVE-2018-0776","markdown":"https://insights.sbomify.com/CVE-2018-0776/index.md","name":"CVE-2018-0776","record":{"aliases":["GHSA-qh4c-h6pf-q28g"],"analysis":{"component_type":"browser","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Microsoft Edge browser","requires_auth":"none","summary":"An attacker can execute arbitrary code in the context of the current user via a memory corruption flaw in the Microsoft Edge scripting engine.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"chakracore","vendor":"microsoft"},{"product":"edge","vendor":"microsoft"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/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":"Microsoft Edge in Windows 10 Gold, 1511, 1607, 1703, 1709, and Windows Server 2016 allows an attacker to execute arbitrary code in the context of the current user, due to how the scripting engine handles objects in memory, aka \"Scripting Engine Memory Corruption Vulnerability\". This CVE ID is unique from CVE-2018-0758, CVE-2018-0762, CVE-2018-0768, CVE-2018-0769, CVE-2018-0770, CVE-2018-0772, CVE-2018-0773, CVE-2018-0774, CVE-2018-0775, CVE-2018-0777, CVE-2018-0778, and CVE-2018-0781.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2018-01-17","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2018-01-17","kind":"exploitdb","ref":"43723","stars":null,"title":"Microsoft Edge Chakra JIT - Stack-to-Heap Copy"}],"tier":"weaponised"},"has_fix":false,"headline":"Memory corruption in Microsoft Edge","id":"CVE-2018-0776","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:chakracore","products":["microsoft:chakracore","microsoft:edge"],"type":"memory_corruption","year":"2018"},"n_packages":0,"n_references":4,"next":{"headline":"Memory corruption in Microsoft Edge","id":"CVE-2018-0777"},"packages":[],"prev":{"headline":"Memory corruption in Microsoft Edge","id":"CVE-2018-0775"},"products":["Microsoft Edge"],"published":"2018-01-04","related":[{"cvss_score":7.5,"headline":"ChakraCore Scripting Engine Type Confusion","id":"CVE-2018-8298","kev_date_added":"2022-03-03","published":"2018-07-11"},{"cvss_score":4.2,"headline":"Microsoft Edge and Internet Explorer Memory Corruption","id":"CVE-2020-0878","kev_date_added":"2021-11-03","published":"2020-09-11"},{"cvss_score":9.8,"headline":"ChakraCore RCE Vulnerability","id":"CVE-2018-8500","kev_date_added":null,"published":"2018-10-10"},{"cvss_score":9.8,"headline":"ChakraCore vulnerable to privilege escalation","id":"CVE-2017-11767","kev_date_added":null,"published":"2017-11-02"},{"cvss_score":9.8,"headline":"ChakraCore RCE Vulnerability","id":"CVE-2017-8658","kev_date_added":null,"published":"2017-08-11"},{"cvss_score":8.8,"headline":"Scripting Engine Memory Corruption Vulnerability","id":"CVE-2020-1555","kev_date_added":null,"published":"2020-08-17"},{"cvss_score":8.1,"headline":"ChakraCore RCE Vulnerability","id":"CVE-2020-1073","kev_date_added":null,"published":"2020-06-09"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["Microsoft Corporation"]},"summary":"An attacker can execute arbitrary code in the context of the current user via a memory corruption flaw in the Microsoft Edge scripting engine.","url":"https://insights.sbomify.com/CVE-2018-0776/"}