CVE-2013-3897
Microsoft Internet Explorer Use-After-Free Vulnerability
Microsoft Internet Explorer
Use-after-free vulnerability in the CDisplayPointer class in mshtml.dll in Microsoft Internet Explorer 6 through 11 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via crafted JavaScript code that uses the onpropertychange event handler, as exploited in the wild in September and October 2013, aka "Internet Explorer Memory Corruption Vulnerability."
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 3 March 2022. US federal agencies were required to remediate it by 24 March 2022.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 77.3%, 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:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2013-3897 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2013-3897.
What does CVE-2013-3897 affect?
CVE-2013-3897 affects Microsoft Internet Explorer. Use-after-free vulnerability in the CDisplayPointer class in mshtml.dll in Microsoft Internet Explorer 6 through 11 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via crafted JavaScript code that uses the onpropertychange event handler, as exploited in the wild in September and October 2013, aka "Internet Explorer Memory Corruption Vulnerability."
How severe is CVE-2013-3897?
CVE-2013-3897 is rated HIGH with a CVSS base score of 8.8. EPSS puts the probability of exploitation in the next 30 days at 77.3%, higher than 99.6% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 24 March 2022.
How should organisations respond to CVE-2013-3897?
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.