Skip to content
Server Security Center
KEVcritical9.8 Used in ransomware campaigns

CVE-2012-4681: Oracle Java SE Runtime Environment (JRE) Arbitrary Code Execution

Oracle Java SE · listed in the CISA catalog of actively exploited vulnerabilities since 2022-03-03.

CVSS v3.1 (CISA ADP)
9.8
critical
EPSS (exploit probability, 30 days)
99%
among the highest 0.1% of all CVEs
Added to CISA KEV
2022-03-03
US federal due date 2022-03-24
Automatable (CISA SSVC)
yes
technical impact: total

What is CVE-2012-4681?

Multiple vulnerabilities in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 6 and earlier allow remote attackers to execute arbitrary code via a crafted applet that bypasses SecurityManager restrictions by (1) using com.sun.beans.finder.ClassFinder.findClass and leveraging an exception with the forName method to access restricted classes from arbitrary packages such as sun.awt.SunToolkit, then (2) using "reflection with a trusted immediate caller" to leverage the getField method to access and modify private fields, as exploited in the wild in August 2012 using Gondzz.class and Gondvv.class.

CISA required action: Apply updates per vendor instructions.

CISA notes

How to fix it

  • The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
  • Vendor advisory: oracle.com/technetwork/topics/security/alert-cve-2012-468…
  • CISA's deadline for US federal agencies: 2022-03-24 (passed) – a useful benchmark for everyone else, too.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-284 Improper Access Control

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.