{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-8617 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-8617 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-8617 is a high-severity memory corruption vulnerability in Microsoft Edge, published on 11 Jul 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-8617 and fix it if it is affected.\n\nWhat it is: CVE-2017-8617 is a high-severity memory corruption vulnerability in Microsoft Edge, published on 11 Jul 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-8617 in the wild and no public exploit code.\n\nAffected product: Microsoft Edge. 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-8617/ (Markdown: https://insights.sbomify.com/CVE-2017-8617/index.md)","id":"CVE-2017-8617","markdown":"https://insights.sbomify.com/CVE-2017-8617/index.md","name":"CVE-2017-8617","record":{"aliases":["GHSA-9f67-m6v3-rwjm"],"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":"Remote attackers can execute arbitrary code via memory handling flaws in Microsoft Edge scripting engines.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"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-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"Microsoft Edge in Windows 10 1703 Microsoft Edge allows a remote code execution vulnerability in the way affected Microsoft scripting engines render when handling objects in memory, aka \"Microsoft Edge Remote Code Execution Vulnerability.\"","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 Windows 10 1703","id":"CVE-2017-8617","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:edge","products":["microsoft:edge"],"type":"memory_corruption","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in Windows 7 SP1, Windows Server 2008 R2 SP1, Windows 8.1 and Windows RT 8.1, Windows Server 2012 and R2, Windows 10 Gold, 1511, 1607, and 1703, and Windows Server 2016","id":"CVE-2017-8618"},"packages":[],"prev":{"headline":"Privilege escalation in Azure AD Connect","id":"CVE-2017-8613"},"products":["Windows 10 1703"],"published":"2017-07-11","related":[{"cvss_score":8.8,"headline":"Microsoft Internet Explorer Memory Corruption","id":"CVE-2021-26411","kev_date_added":"2021-11-03","published":"2021-03-11"},{"cvss_score":8.8,"headline":"Microsoft Edge Memory Corruption","id":"CVE-2016-7200","kev_date_added":"2022-03-28","published":"2016-11-10"},{"cvss_score":8.8,"headline":"Microsoft Edge Memory Corruption","id":"CVE-2016-7201","kev_date_added":"2022-03-28","published":"2016-11-10"},{"cvss_score":8.1,"headline":"Microsoft Edge and Internet Explorer Type Confusion","id":"CVE-2017-0037","kev_date_added":"2022-03-28","published":"2017-02-26"},{"cvss_score":6.5,"headline":"Microsoft Internet Explorer and Edge Information Disclosure","id":"CVE-2016-3351","kev_date_added":"2022-05-24","published":"2016-09-14"},{"cvss_score":9.8,"headline":"Memory corruption in Microsoft ChakraCore","id":"CVE-2017-0028","kev_date_added":null,"published":"2017-07-14"},{"cvss_score":9.8,"headline":"ChakraCore RCE Vulnerability","id":"CVE-2017-0223","kev_date_added":null,"published":"2017-05-15"}],"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-09-17","vendors":["Microsoft Corporation"]},"summary":"Remote attackers can execute arbitrary code via memory handling flaws in Microsoft Edge scripting engines.","url":"https://insights.sbomify.com/CVE-2017-8617/"}