{"answers":{"affected":"2 open source packages ship an affected version, including Microsoft.ChakraCore. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-0818 in the wild and no public exploit code.","fix":"Upgrade Microsoft.ChakraCore to 1.8.0 or later.","what":"CVE-2018-0818 is a high-severity vulnerability in Microsoft Chakracore, published on 10 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-0818 and fix it if it is affected.\n\nWhat it is: CVE-2018-0818 is a high-severity vulnerability in Microsoft Chakracore, published on 10 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: There is no known exploitation of CVE-2018-0818 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- Microsoft.ChakraCore (NuGet): affected all versions; fixed in 1.8.0\n- Microsoft.ChakraCore (NuGet): affected all versions; fixed in 1.8.0\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-0818/ (Markdown: https://insights.sbomify.com/CVE-2018-0818/index.md)","id":"CVE-2018-0818","markdown":"https://insights.sbomify.com/CVE-2018-0818/index.md","name":"CVE-2018-0818","record":{"aliases":["GHSA-fv8m-p45w-gf38"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"ChakraCore JavaScript engine","requires_auth":"none","summary":"Attackers can bypass Control Flow Guard in ChakraCore to execute arbitrary code when combined with another vulnerability.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"chakracore","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":[],"description":"Microsoft ChakraCore allows an attacker to bypass Control Flow Guard (CFG) in conjunction with another vulnerability to run arbitrary code on a target system, due to how the Chakra scripting engine handles accessing memory, aka \"Scripting Engine Security Feature Bypass\".","ecosystems":["NuGet"],"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":"ChakraCore RCE Vulnerability","id":"CVE-2018-0818","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"NuGet","product":"microsoft:chakracore","products":["microsoft:chakracore"],"type":"security_feature_bypass","year":"2018"},"n_packages":2,"n_references":2,"next":{"headline":"Other in Microsoft Office 2016 for Mac","id":"CVE-2018-0819"},"packages":[{"ecosystem":"NuGet","fixed":["1.8.0"],"introduced":["0"],"last_affected":[],"package":"Microsoft.ChakraCore","purl":null,"source":"GHSA-fv8m-p45w-gf38"},{"ecosystem":"NuGet","fixed":["1.8.0"],"introduced":["0"],"last_affected":[],"package":"Microsoft.ChakraCore","purl":"pkg:nuget/Microsoft.ChakraCore","source":"GHSA-fv8m-p45w-gf38"}],"prev":{"headline":"Use after free in Windows","id":"CVE-2018-0817"},"products":["ChakraCore"],"published":"2018-01-10","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":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["Microsoft Corporation"]},"summary":"Attackers can bypass Control Flow Guard in ChakraCore to execute arbitrary code when combined with another vulnerability.","url":"https://insights.sbomify.com/CVE-2018-0818/"}