CVE-2013-3163
Microsoft Internet Explorer Memory Corruption Vulnerability
Microsoft Internet Explorer
Microsoft Internet Explorer 8 through 10 allows 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," a different vulnerability than CVE-2013-3144 and CVE-2013-3151.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 30 March 2023. US federal agencies were required to remediate it by 20 April 2023.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 70.7%, which is higher than 99.4% 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-3163 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2013-3163.
What does CVE-2013-3163 affect?
CVE-2013-3163 affects Microsoft Internet Explorer. Microsoft Internet Explorer 8 through 10 allows 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," a different vulnerability than CVE-2013-3144 and CVE-2013-3151.
How severe is CVE-2013-3163?
CVE-2013-3163 is rated HIGH with a CVSS base score of 8.8. EPSS puts the probability of exploitation in the next 30 days at 70.7%, higher than 99.4% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 20 April 2023.
How should organisations respond to CVE-2013-3163?
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.