Threats / Oracle / CVE-2012-1723
CVE-2012-1723
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Oracle Java SE vulnerability
Unspecified vulnerability in Oracle Java SE's Hotspot component allows remote attackers to compromise confidentiality, integrity, and availability through unknown vectors.
Verdict
Today item, not a backlog item.
This vulnerability poses critical risk due to high EPSS score, active exploitation in the wild, and association with ransomware campaigns. Remote exploitation without authentication makes it a priority for immediate patching across Java SE deployments.
CISA KEV Yes · 2022-03-034Ransomware use Flagged4EPSS 0.93688 (verify live)5Exploit Public PoC6CVSS 9.8 (CISA)3CISA SSVC Exploitation: active · Automatable: rapid · 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
20 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.93688 — 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: rapid · 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 3547 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 deliver malicious Java bytecode or applet to a target system running vulnerable Java SE.
Business
Attackers gain arbitrary code execution capability on affected endpoints, enabling lateral movement and persistence.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I exploit the Hotspot JIT compiler vulnerability to bypass security restrictions and execute native code.
Business
Confidentiality, integrity, and availability of systems are compromised; data exfiltration and system manipulation become possible.
3
Lateral reach — past segmentation narrative 3
Attacker
I deploy ransomware or data-stealing malware through the compromised Java runtime environment.
Business
Organizations face operational disruption, financial extortion demands, regulatory penalties, and reputational damage from ransomware deployment.
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