CVE-2012-4792
Microsoft Internet Explorer Use-After-Free Vulnerability
Microsoft Internet Explorer
Use-after-free vulnerability in Microsoft Internet Explorer 6 through 8 allows remote attackers to execute arbitrary code via a crafted web site that triggers access to an object that (1) was not properly allocated or (2) is deleted, as demonstrated by a CDwnBindInfo object, and exploited in the wild in December 2012.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 23 July 2024. US federal agencies were required to remediate it by 13 August 2024.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 78.8%, 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-2012-4792 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2012-4792.
What does CVE-2012-4792 affect?
CVE-2012-4792 affects Microsoft Internet Explorer. Use-after-free vulnerability in Microsoft Internet Explorer 6 through 8 allows remote attackers to execute arbitrary code via a crafted web site that triggers access to an object that (1) was not properly allocated or (2) is deleted, as demonstrated by a CDwnBindInfo object, and exploited in the wild in December 2012.
How severe is CVE-2012-4792?
CVE-2012-4792 is rated HIGH with a CVSS base score of 8.8. EPSS puts the probability of exploitation in the next 30 days at 78.8%, higher than 99.6% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 13 August 2024.
How should organisations respond to CVE-2012-4792?
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.