CVE-2011-2462
Adobe Reader and Acrobat Universal 3D Memory Corruption Vulnerability
Adobe Reader and Acrobat
Unspecified vulnerability in the U3D component in Adobe Reader and Acrobat 10.1.1 and earlier on Windows and Mac OS X, and Adobe Reader 9.x through 9.4.6 on UNIX, allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via unknown vectors, as exploited in the wild in December 2011.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 8 June 2022. US federal agencies were required to remediate it by 22 June 2022.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 88.6%, which is higher than 99.8% 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:H/I:H/A:H
Frequently asked questions
Is CVE-2011-2462 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2011-2462.
What does CVE-2011-2462 affect?
CVE-2011-2462 affects Adobe Reader and Acrobat. Unspecified vulnerability in the U3D component in Adobe Reader and Acrobat 10.1.1 and earlier on Windows and Mac OS X, and Adobe Reader 9.x through 9.4.6 on UNIX, allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via unknown vectors, as exploited in the wild in December 2011.
How severe is CVE-2011-2462?
CVE-2011-2462 is rated CRITICAL with a CVSS base score of 9.8. EPSS puts the probability of exploitation in the next 30 days at 88.6%, higher than 99.8% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 22 June 2022.
How should organisations respond to CVE-2011-2462?
Apply the vendor patch for Adobe Reader and Acrobat 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.