Skip to content
CTI Academy Sponsor CTI Academy
CRITICAL · CVSS 9.8 CISA Known Exploited Vulnerability

CVE-2012-5076

Oracle Java SE Sandbox Bypass Vulnerability

Oracle Java SE

Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 7 and earlier allows remote attackers to affect confidentiality, integrity, and availability, related to JAX-WS.

CVSS
9.8
CRITICAL
EPSS
91.3%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
16 Oct 2012
CWE-284

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 28 March 2022. US federal agencies were required to remediate it by 18 April 2022.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 91.3%, 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-5076 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2012-5076.

What does CVE-2012-5076 affect?

CVE-2012-5076 affects Oracle Java SE. Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 7 and earlier allows remote attackers to affect confidentiality, integrity, and availability, related to JAX-WS.

How severe is CVE-2012-5076?

CVE-2012-5076 is rated CRITICAL with a CVSS base score of 9.8. EPSS puts the probability of exploitation in the next 30 days at 91.3%, higher than 99.8% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 18 April 2022.

How should organisations respond to CVE-2012-5076?

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.