CVE-2017-0037
Microsoft Edge and Internet Explorer Type Confusion Vulnerability
Microsoft Edge and Internet Explorer
Microsoft Internet Explorer 10 and 11 and Microsoft Edge have a type confusion issue in the Layout::MultiColumnBoxBuilder::HandleColumnBreakOnColumnSpanningElement function in mshtml.dll, which allows remote attackers to execute arbitrary code via vectors involving a crafted Cascading Style Sheets (CSS) token sequence and crafted JavaScript code that operates on a TH element.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 28 March 2022. US federal agencies were required to remediate it by 18 April 2022.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 80.4%, which is higher than 99.6% 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:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2017-0037 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2017-0037.
What does CVE-2017-0037 affect?
CVE-2017-0037 affects Microsoft Edge and Internet Explorer. Microsoft Internet Explorer 10 and 11 and Microsoft Edge have a type confusion issue in the Layout::MultiColumnBoxBuilder::HandleColumnBreakOnColumnSpanningElement function in mshtml.dll, which allows remote attackers to execute arbitrary code via vectors involving a crafted Cascading Style Sheets (CSS) token sequence and crafted JavaScript code that operates on a TH element.
How severe is CVE-2017-0037?
CVE-2017-0037 is rated HIGH with a CVSS base score of 8.1. EPSS puts the probability of exploitation in the next 30 days at 80.4%, higher than 99.6% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 18 April 2022.
How should organisations respond to CVE-2017-0037?
Apply the vendor patch for Microsoft Edge and 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.