{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-0201 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-0201 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-0201 is a high-severity memory corruption vulnerability in Microsoft Internet Explorer, published on 12 Apr 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-0201 and fix it if it is affected.\n\nWhat it is: CVE-2017-0201 is a high-severity memory corruption vulnerability in Microsoft Internet Explorer, published on 12 Apr 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-0201 in the wild and no public exploit code.\n\nAffected product: Microsoft Internet Explorer. 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-0201/ (Markdown: https://insights.sbomify.com/CVE-2017-0201/index.md)","id":"CVE-2017-0201","markdown":"https://insights.sbomify.com/CVE-2017-0201/index.md","name":"CVE-2017-0201","record":{"aliases":["GHSA-4vg7-vv27-xc6x"],"analysis":{"component_type":"browser","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Internet Explorer","requires_auth":"none","summary":"Remote attackers can execute arbitrary code via memory corruption in Internet Explorer's scripting engines.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"internet_explorer","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":"A remote code execution vulnerability exists in Internet Explorer in the way that the JScript and VBScript engines render when handling objects in memory. The vulnerability could corrupt memory in such a way that an attacker could execute arbitrary code in the context of the current user, aka \"Scripting Engine Memory Corruption Vulnerability.\" This CVE ID is unique from CVE-2017-0093.","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 Internet Explorer","id":"CVE-2017-0201","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:internet_explorer","products":["microsoft:internet_explorer"],"type":"memory_corruption","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in Internet Explorer","id":"CVE-2017-0202"},"packages":[],"prev":{"headline":"Memory corruption in Edge","id":"CVE-2017-0200"},"products":["Internet Explorer"],"published":"2017-04-12","related":[{"cvss_score":9.8,"headline":"Microsoft Internet Explorer Memory Corruption","id":"CVE-2014-1776","kev_date_added":"2022-01-28","published":"2014-04-27"},{"cvss_score":8.8,"headline":"Microsoft Internet Explorer Remote Code Execution","id":"CVE-2021-27085","kev_date_added":"2021-11-03","published":"2021-03-11"},{"cvss_score":8.8,"headline":"Microsoft Internet Explorer Remote Code Execution","id":"CVE-2017-0222","kev_date_added":"2022-02-25","published":"2017-05-12"},{"cvss_score":8.8,"headline":"Microsoft Internet Explorer Privilege Escalation","id":"CVE-2017-0210","kev_date_added":"2022-05-24","published":"2017-04-12"},{"cvss_score":8.8,"headline":"Microsoft Internet Explorer Memory Corruption","id":"CVE-2017-0149","kev_date_added":"2022-05-24","published":"2017-03-17"},{"cvss_score":8.8,"headline":"Microsoft Internet Explorer Memory Corruption","id":"CVE-2015-2502","kev_date_added":"2022-04-13","published":"2015-08-19"},{"cvss_score":8.8,"headline":"Microsoft Internet Explorer Memory Corruption","id":"CVE-2015-2419","kev_date_added":"2022-03-28","published":"2015-07-14"}],"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":["Microsoft Corporation"]},"summary":"Remote attackers can execute arbitrary code via memory corruption in Internet Explorer's scripting engines.","url":"https://insights.sbomify.com/CVE-2017-0201/"}