Threats / Oracle / CVE-2010-0840
CVE-2010-0840
· 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 compromise confidentiality, integrity, and availability through unknown attack vectors.
Verdict
Today item — known-exploited.
This vulnerability in Java SE poses significant risk due to high exploitability (EPSS 0.92) and confirmed active exploitation. The unspecified nature and broad impact scope (CIA triad) suggest a critical remote code execution or similar severe flaw affecting Java applications.
CISA KEV Yes · 2022-05-254EPSS 0.96319 (verify live)5CVSS 9.8 (CISA)3CISA SSVC Exploitation: active · Automatable: yes · Impact: total3Exploit 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).
Probability (EPSS)
EPSS 0.96319 — 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 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: 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 4437 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 identify that the target runs a vulnerable Java Runtime Environment version and craft a malicious payload leveraging the unspecified vector.
Business
Attackers gain remote code execution capability against any system running affected JRE versions, enabling widespread compromise of enterprise infrastructure.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I deliver the exploit through network-accessible Java applications or applets without requiring user interaction beyond normal application use.
Business
Organizations face rapid lateral movement and persistence across systems where Java is deployed, from desktops to servers.
3
Lateral reach — past segmentation narrative 3
Attacker
I establish control over compromised systems to exfiltrate data, modify files, or install persistent backdoors.
Business
Data breaches, system integrity violations, and operational disruption occur across the affected environment.
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