Threats / Oracle / CVE-2012-4681
CVE-2012-4681
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-19
Oracle Java SE vulnerability
Oracle Java SE contains a remote code execution vulnerability in the Java Runtime Environment that allows unauthenticated attackers to execute arbitrary code on affected systems.
Verdict
Today item, not a backlog item.
CVE-2012-4681 is a critical remote code execution flaw in Oracle Java SE's JRE component. With an EPSS score of 0.9414 and confirmed exploitation in the wild including ransomware campaigns, this vulnerability poses severe risk to any system running vulnerable Java versions.
CISA KEV Yes · 2022-03-034Ransomware use Flagged4EPSS 0.98536 (verify live)5Exploit Public PoC6CVSS 9.8 (CISA)3CISA SSVC Exploitation: active · Automatable: yes · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
12 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-03-03), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.98536 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: Oracle, Java SE. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 3474 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious Java applet or exploit code targeting the JRE vulnerability and deliver it via a compromised or attacker-controlled website.
Business
End users visiting compromised web content unknowingly trigger code execution on their systems, leading to potential data theft, system compromise, or ransomware infection.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I execute arbitrary code with the privileges of the user running the Java application, establishing persistence and lateral movement capabilities.
Business
Attackers gain foothold in enterprise networks, enabling ransomware deployment, credential harvesting, and further infrastructure compromise.
3
Lateral reach — past segmentation narrative 3
Attacker
I deploy ransomware payloads across compromised systems to encrypt critical business data and demand ransom payments.
Business
Organizations face operational shutdown, data loss, financial extortion, regulatory penalties, and reputational damage from widespread ransomware incidents.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by mitreCNA
Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.