CVE-2016-3298
Microsoft Internet Explorer Messaging API Information Disclosure Vulnerability
Microsoft Internet Explorer
Microsoft Internet Explorer 9 through 11 and the Internet Messaging API in Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, and Windows 7 SP1 allow remote attackers to determine the existence of arbitrary files via a crafted web site, aka "Internet Explorer Information Disclosure Vulnerability."
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 24 May 2022. US federal agencies were required to remediate it by 14 June 2022.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 33.3%, which is higher than 98.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:N/A:N
Frequently asked questions
Is CVE-2016-3298 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2016-3298.
What does CVE-2016-3298 affect?
CVE-2016-3298 affects Microsoft Internet Explorer. Microsoft Internet Explorer 9 through 11 and the Internet Messaging API in Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, and Windows 7 SP1 allow remote attackers to determine the existence of arbitrary files via a crafted web site, aka "Internet Explorer Information Disclosure Vulnerability."
How severe is CVE-2016-3298?
CVE-2016-3298 is rated MEDIUM with a CVSS base score of 6.5. EPSS puts the probability of exploitation in the next 30 days at 33.3%, higher than 98.4% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 14 June 2022.
How should organisations respond to CVE-2016-3298?
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.