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

Oracle ADF Faces vulnerability

Oracle ADF Faces contains an unsafe deserialization vulnerability allowing unauthenticated remote code execution. The flaw affects the library included in Oracle JDeveloper Distribution.

Verdict

Today item — known-exploited.

An unauthenticated attacker can exploit unsafe deserialization of untrusted data in Oracle ADF Faces to achieve remote code execution without authentication, posing critical risk to affected deployments.

CISA KEV Yes · 2024-09-183EPSS 0.6201 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
2 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 2024-09-18).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.6201 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Oracle, ADF Faces. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-502 Deserialization of Untrusted Data — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
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 craft a malicious serialized Java object and send it to an exposed ADF Faces endpoint.
Business
The organization's application server processes untrusted input without validation, creating an entry point for attackers.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
The vulnerable deserialization logic instantiates my malicious object, triggering gadget chain execution during object reconstruction.
Business
Arbitrary code executes with the privileges of the application server process, bypassing all authentication controls.
3

Lateral reach — past segmentation narrative 3

Attacker
I gain command execution on the underlying system and establish persistence or exfiltrate sensitive data.
Business
Attackers achieve full system compromise, enabling data theft, lateral movement, and operational disruption without credentials.
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)
  • Weaponized exploit available (VulnCheck)
  • 2 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • 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.