Threats / Oracle / CVE-2020-14644
CVE-2020-14644
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Oracle WebLogic Server vulnerability
Oracle WebLogic Server contains an unauthenticated deserialization vulnerability in T3/IIOP protocols allowing remote code execution. Actively exploited in the wild with high exploit probability.
Verdict
Today item — known-exploited.
Unauthenticated network attackers can exploit unsafe deserialization in WebLogic Server's T3 and IIOP protocol handlers to execute arbitrary code without authentication, enabling full system compromise.
CISA KEV Yes · 2024-09-185EPSS 0.94465 (verify live)6CVSS 9.83CISA SSVC Exploitation: active · Automatable: yes · Impact: total4Exploit Public PoC / detection · nuclei template11
01
Is it exploitable?
— the evidence, ranked above the scoreReported 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).
Probability (EPSS)
EPSS 0.94465 — 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, WebLogic Server. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
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 1526 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 public proof-of-concept / detection template). Catalog entries: nuclei template. 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 craft a malicious serialized Java object and send it via T3 or IIOP protocol to an exposed WebLogic Server instance.
Business
Attacker gains unauthenticated code execution on critical middleware infrastructure, bypassing all access controls.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I trigger deserialization of the malicious payload within the WebLogic process, causing arbitrary code execution with server privileges.
Business
Entire application server and hosted applications are compromised, enabling data theft, lateral movement, and operational disruption.
3
Lateral reach — past segmentation narrative 3
Attacker
I establish persistent access and move laterally through the enterprise network from the compromised middleware tier.
Business
Breach scope expands beyond WebLogic to connected systems, databases, and sensitive business operations.
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