CVE-2014-0322
Microsoft Internet Explorer Use-After-Free Vulnerability
Microsoft Internet Explorer
Use-after-free vulnerability in Microsoft Internet Explorer 9 and 10 allows remote attackers to execute arbitrary code via vectors involving crafted JavaScript code, CMarkup, and the onpropertychange attribute of a script element, as exploited in the wild in January and February 2014.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 4 May 2022. US federal agencies were required to remediate it by 25 May 2022.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 85.1%, which is higher than 99.7% 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-2014-0322 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2014-0322.
What does CVE-2014-0322 affect?
CVE-2014-0322 affects Microsoft Internet Explorer. Use-after-free vulnerability in Microsoft Internet Explorer 9 and 10 allows remote attackers to execute arbitrary code via vectors involving crafted JavaScript code, CMarkup, and the onpropertychange attribute of a script element, as exploited in the wild in January and February 2014.
How severe is CVE-2014-0322?
CVE-2014-0322 is rated HIGH with a CVSS base score of 8.8. EPSS puts the probability of exploitation in the next 30 days at 85.1%, higher than 99.7% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 25 May 2022.
How should organisations respond to CVE-2014-0322?
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.