CVE-2012-1723
Oracle Java SE Runtime Environment (JRE) Arbitrary Code Execution Vulnerability
Oracle Java SE
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 update 4 and earlier, 6 update 32 and earlier, 5 update 35 and earlier, and 1.4.2_37 and earlier allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to Hotspot.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 3 March 2022. US federal agencies were required to remediate it by 24 March 2022. CISA records this vulnerability as known to be used in ransomware campaigns.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 93.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-2012-1723 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2012-1723.
What does CVE-2012-1723 affect?
CVE-2012-1723 affects Oracle Java SE. Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 update 4 and earlier, 6 update 32 and earlier, 5 update 35 and earlier, and 1.4.2_37 and earlier allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to Hotspot.
How severe is CVE-2012-1723?
CVE-2012-1723 is rated CRITICAL with a CVSS base score of 9.8. EPSS puts the probability of exploitation in the next 30 days at 93.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 24 March 2022.
How should organisations respond to CVE-2012-1723?
Apply the vendor patch for Oracle Java SE 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.