dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 9 Oct 2024.
Weblogic ServerApplication · Oracle

CVE-2020-14644

CRITICAL · 9.8 CVSS v3.1 Published 2020-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Vulnerability in the Oracle WebLogic Server product of Oracle Fusion Middleware (component: Core). Supported versions that are affected are 12.2.1.3.0, 12.2.1.4.0 and 14.1.1.0.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via IIOP, T3 to compromise Oracle WebLogic Server. Successful attacks of this vulnerability can result in takeover of Oracle WebLogic Server. CVSS 3.1 Base Score 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Oracle WebLogic Server contains a critical deserialization vulnerability in the Core component affecting versions 12.2.1.3.0, 12.2.1.4.0, and 14.1.1.0.0. Unauthenticated remote attackers can exploit this via IIOP or T3 network protocols to achieve complete server takeover, gaining full confidentiality, integrity, and availability control.

MitigationApply the Oracle Critical Patch Update immediately. If patching is not immediately feasible, restrict network access to IIOP and T3 ports (7001, 7002 and related) or disable these protocols entirely if not required.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Weblogic ServerApplication
Affected:= 12.2.1.3.0= 12.2.1.4.0= 14.1.1.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm WebLogic Server installation
    Locate the WebLogic installation directory (typically ORACLE_HOME orMiddleware_HOME). Check for the presence of wlserver_*.jar or the registry.xml/registry.dat file in the Oracle inventory directory.
    Affected if WebLogic Server is not present on the system, the vulnerability does not apply.
  2. Identify installed WebLogic version
    Open the registry.xml file in the Oracle inventory (usually in /etc/oraInst.loc on Linux or the inventory directory on Windows). Alternatively, check the manifest file in the WebLogic installation or run: java -jar wlserver_*.jar -mode=console and check the version output.
    Affected if The installed version matches 12.2.1.3.0, 12.2.1.4.0, or 14.1.1.0.0 exactly.
  3. Verify T3 protocol is enabled
    Check the WebLogic Server configuration files (config.xml) in the domain directory. Look for NetworkAccessPoint or ServerMBean entries with T3 protocol configured. Also check the Administration Console under Servers > Protocols > T3.
    Affected if T3 protocol is enabled and accessible on the network, the deserialization flaw can be exploited via T3.
  4. Verify IIOP protocol is enabled
    Check the WebLogic Server configuration files (config.xml) for IIOP configuration. Look for IIOPMBean or IIOP entries. In the Administration Console, check Servers > Protocols > IIOP.
    Affected if IIOP protocol is enabled and accessible on the network, the deserialization flaw can be exploited via IIOP.
  5. Assess network exposure of WebLogic ports
    Identify the listen ports for the WebLogic Server (default 7001 for admin, 7002 for admin with SSL). Use netstat or ss commands to determine if these ports are exposed to untrusted networks or the internet.
    Affected if WebLogic ports (T3/IIOP) are reachable from untrusted network segments or the internet, making remote exploitation possible.

The system is affected if WebLogic Server versions 12.2.1.3.0, 12.2.1.4.0, or 14.1.1.0.0 are installed with T3 or IIOP protocols enabled and accessible from the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Oracle Critical Patch Update immediately. If patching is not immediately feasible, restrict network access to IIOP and T3 ports (7001, 7002 and related) or disable these protocols entirely if not required.

Recommended fix High confidence

Oracle WebLogic Server 14.1.1.0.2 or later (or apply July 2020 Critical Patch Update)

  1. Download and apply Oracle Critical Patch Update (CPU) July 2020 or later which includes the fix for CVE-2020-14644
  2. For 12.2.1.3.0: Apply patch 31335037 or upgrade to 12.2.1.3.1 with the July 2020 CPU
  3. For 12.2.1.4.0: Apply patch 31335038 or upgrade to 12.2.1.4.1 with the July 2020 CPU
  4. For 14.1.1.0.0: Apply patch 31335039 or upgrade to 14.1.1.0.1 with the July 2020 CPU
  5. Alternatively, upgrade to WebLogic Server 14.1.1.0.2 or later which includes the security fix
  6. Ensure to backup the WebLogic domain before applying patches
  7. Restart WebLogic Server after applying the patch
Caveat Patches may require WebLogic Server restart; ensure testing in non-production environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Weblogic Server Exploited in the wild — priority engagement
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-14644 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-14644 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data