Threats / Oracle / CVE-2013-0431
CVE-2013-0431
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Oracle Java Runtime Environment (JRE) vulnerability
Unspecified vulnerability in Oracle Java Runtime Environment allows remote attackers to bypass the Java security sandbox, enabling arbitrary code execution.
Verdict
Today item, not a backlog item.
This sandbox escape vulnerability poses critical risk. Active exploitation in the wild and association with ransomware campaigns demonstrate immediate threat. Organizations running Java applications face direct compromise risk without patching.
CISA KEV Yes · 2022-05-254Ransomware use Flagged4EPSS 0.89987 (verify live)5CVSS 5.3 (CISA)3CISA SSVC Exploitation: active · Automatable: yes · Impact: partial3Exploit Weaponized · public exploit · Metasploit module11
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
4 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-05-25), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.89987 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 5.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) · Affected: Oracle, Java Runtime Environment (JRE). 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: partialCISA'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 3401 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 applet or application to a target system via web browser or email.
Business
End-user systems become vulnerable to remote code execution without user awareness of the threat.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I exploit the sandbox bypass to execute arbitrary code with the privileges of the Java process.
Business
Attacker gains foothold on the network with ability to move laterally and establish persistence.
3
Lateral reach — past segmentation narrative 3
Attacker
I deploy ransomware or data exfiltration tools across compromised systems.
Business
Organization suffers operational disruption, data loss, and financial extortion demands.
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