dbcve.org
Weblogic ServerApplication · Oracle

CVE-2020-14825

CRITICAL · 9.8 CVSS v3.1 Published 2020-10-21
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
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

Critical remote code execution vulnerability in Oracle WebLogic Server Core component (versions 12.2.1.3.0, 12.2.1.4.0, 14.1.1.0.0). Easily exploitable via unauthenticated network access through IIOP or T3 protocols, allowing complete takeover of the affected WebLogic Server instance.

MitigationApply Oracle Critical Patch Update (CPU) patches for CVE-2020-14825 immediately. If patching is not immediately feasible, restrict network access to IIOP and T3 ports or disable these protocols until patches can be applied.

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. Identify WebLogic Server installation
    Locate the WebLogic installation directory (typically under Oracle Middleware home). Check for product directories such as wlserver_12.2.1, wlserver_12.2.1.4, or wlserver_14.1.1. Look for the registry.xml or inventory.xml file in the Oracle home directory to confirm installation.
    Affected if WebLogic Server is installed in the environment
  2. Confirm installed WebLogic version
    Read the version file in the WebLogic installation, typically found in the product directory (for example, in the root of the wlserver directory) or check the Oracle inventory file. Compare the version to the affected ranges: 12.2.1.3.0, 12.2.1.4.0, or 14.1.1.0.0.
    Affected if The installed version exactly matches 12.2.1.3.0, 12.2.1.4.0, or 14.1.1.0.0
  3. Check if IIOP protocol is enabled
    Review the WebLogic Server configuration files (config.xml) in the domain directory. Look for <iiop> or <iiop-machine> elements, or check for IIOP-related settings in the WebLogic Administration Console under the Protocols submenu for each server instance.
    Affected if IIOP protocol is enabled in the WebLogic Server configuration
  4. Check if T3 protocol is enabled
    Review the WebLogic Server configuration files (config.xml) in the domain directory. Look for <t3> or <t3-machine> elements, or check for T3-related settings in the WebLogic Administration Console under the Protocols submenu for each server instance.
    Affected if T3 protocol is enabled in the WebLogic Server configuration
  5. Verify network exposure of IIOP and T3 ports
    Identify the configured IIOP and T3 listener ports (typically 7001 for admin or ranges above 7001 for managed servers). Use network scanning tools (such as netstat, nmap, or the WebLogic Administration Console) to determine if these ports are accessible from untrusted networks.
    Affected if IIOP or T3 ports are exposed to untrusted network access

The environment is affected if WebLogic Server version 12.2.1.3.0, 12.2.1.4.0, or 14.1.1.0.0 is installed AND IIOP or T3 protocol is enabled AND these ports are network-accessible to unauthenticated attackers.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Update (CPU) patches for CVE-2020-14825 immediately. If patching is not immediately feasible, restrict network access to IIOP and T3 ports or disable these protocols until patches can be applied.

Fix this in Weblogic Server Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-14825 — 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-14825 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