{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2017-11874 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-11874 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-11874 is a low-severity vulnerability in Microsoft Chakracore, published on 15 Nov 2017. 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-2017-11874 and fix it if it is affected.\n\nWhat it is: CVE-2017-11874 is a low-severity vulnerability in Microsoft Chakracore, published on 15 Nov 2017. 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-2017-11874 in the wild and no public exploit code.\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-2017-11874/ (Markdown: https://insights.sbomify.com/CVE-2017-11874/index.md)","id":"CVE-2017-11874","markdown":"https://insights.sbomify.com/CVE-2017-11874/index.md","name":"CVE-2017-11874","record":{"aliases":["GHSA-mpq3-wcg8-72j4"],"analysis":{"component_type":"browser","fix_type":"patch","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Microsoft Edge browser","requires_auth":"none","summary":"Attackers can bypass Control Flow Guard in Microsoft Edge to execute arbitrary code via JIT compiler memory handling flaws.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"chakracore","vendor":"microsoft"},{"product":"edge","vendor":"microsoft"}],"cvss":{"score":3.1,"severity":"low","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.0"},"cwes":[],"description":"Microsoft Edge in Microsoft Windows 10 1703, 1709, Windows Server, version 1709, and ChakraCore allows an attacker to bypass Control Flow Guard (CFG) to run arbitrary code on a target system, due to how Microsoft Edge handles accessing memory in code compiled by the Edge Just-In-Time (JIT) compiler, aka \"Microsoft Edge Security Feature Bypass Vulnerability\". This CVE ID is unique from CVE-2017-11863 and CVE-2017-11872.","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":"Security feature bypass in Microsoft Edge","id":"CVE-2017-11874","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:chakracore","products":["microsoft:chakracore","microsoft:edge"],"type":"security_feature_bypass","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site request forgery in Microsoft Server","id":"CVE-2017-11876"},"packages":[],"prev":{"headline":"Memory corruption in ChakraCore, Microsoft Edge","id":"CVE-2017-11873"},"products":["Microsoft Edge"],"published":"2017-11-15","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":"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 Microsoft Edge to execute arbitrary code via JIT compiler memory handling flaws.","url":"https://insights.sbomify.com/CVE-2017-11874/"}