CVE-2017-0149
Microsoft Internet Explorer Memory Corruption Vulnerability
Microsoft Internet Explorer
Microsoft Internet Explorer 9 through 11 allow remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted web site, aka "Internet Explorer Memory Corruption Vulnerability." This vulnerability is different from those described in CVE-2017-0018 and CVE-2017-0037.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 24 May 2022. US federal agencies were required to remediate it by 14 June 2022.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 28.5%, which is higher than 98.2% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2017-0149 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2017-0149.
What does CVE-2017-0149 affect?
CVE-2017-0149 affects Microsoft Internet Explorer. Microsoft Internet Explorer 9 through 11 allow remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted web site, aka "Internet Explorer Memory Corruption Vulnerability." This vulnerability is different from those described in CVE-2017-0018 and CVE-2017-0037.
How severe is CVE-2017-0149?
CVE-2017-0149 is rated HIGH with a CVSS base score of 8.8. EPSS puts the probability of exploitation in the next 30 days at 28.5%, higher than 98.2% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 14 June 2022.
How should organisations respond to CVE-2017-0149?
Apply the vendor patch for Microsoft Internet Explorer as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.