CVE-2013-7331
Microsoft Internet Explorer Information Disclosure Vulnerability
Microsoft Internet Explorer
The Microsoft.XMLDOM ActiveX control in Microsoft Windows 8.1 and earlier allows remote attackers to determine the existence of local pathnames, UNC share pathnames, intranet hostnames, and intranet IP addresses by examining error codes, as demonstrated by a res:// URL, and exploited in the wild in February 2014.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 25 May 2022. US federal agencies were required to remediate it by 15 June 2022.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 50.2%, which is higher than 98.9% 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:N/S:U/C:L/I:N/A:L
Frequently asked questions
Is CVE-2013-7331 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2013-7331.
What does CVE-2013-7331 affect?
CVE-2013-7331 affects Microsoft Internet Explorer. The Microsoft.XMLDOM ActiveX control in Microsoft Windows 8.1 and earlier allows remote attackers to determine the existence of local pathnames, UNC share pathnames, intranet hostnames, and intranet IP addresses by examining error codes, as demonstrated by a res:// URL, and exploited in the wild in February 2014.
How severe is CVE-2013-7331?
CVE-2013-7331 is rated MEDIUM with a CVSS base score of 6.5. EPSS puts the probability of exploitation in the next 30 days at 50.2%, higher than 98.9% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 15 June 2022.
How should organisations respond to CVE-2013-7331?
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.