basicsecurity.net
Proof, not just disclosure.
Threats / Oracle / CVE-2010-0840
CVE-2010-0840 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

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-253EPSS 0.96166 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported 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).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.96166 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Oracle, Java Runtime Environment (JRE). Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

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

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 4 reported-exploitation source(s)
  • Catalogued by oracle (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by oracleCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.