dbcve.org
Weblogic ServerApplication · Oracle

CVE-2020-14645

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
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 10.3.6.0.0, 12.1.3.0.0, 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 vulnerability in its Core component that allows unauthenticated attackers to achieve complete server takeover via IIOP or T3 network protocols. The vulnerability affects versions 10.3.6.0.0 through 14.1.1.0.0 and is easily exploitable over the network without any authentication credentials.

MitigationApply the Oracle Critical Patch Update that addresses CVE-2020-14645, or upgrade to a patched version of WebLogic Server. If immediate patching is not possible, consider restricting network access to IIOP and T3 ports or disabling these protocols 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:= 10.3.6.0.0= 12.1.3.0.0= 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
    Check for WebLogic Server by examining common installation directories such as $ORACLE_HOME or C:\Oracle\Middleware, or search for WebLogic-specific files like weblogic.jar or config.xml in the file system.
    Affected if Oracle WebLogic Server is found on the system
  2. Determine installed WebLogic version
    Locate the version file or check the registry. In typical installations, the version is stored in the product registry file or can be retrieved by examining the manifest within the weblogic.jar file located in the server lib directory.
    Affected if The installed version matches 10.3.6.0.0, 12.1.3.0.0, 12.2.1.3.0, 12.2.1.4.0, or 14.1.1.0.0, or falls within the range 10.3.6.0.0 through 14.1.1.0.0
  3. Verify IIOP protocol is enabled
    Examine the WebLogic Server configuration file (config.xml) for IIOP settings, typically found in the DomainHOME/config directory. Check for <iiop> or <iiop-name> elements, or access the WebLogic Administration Console and navigate to the Server > Protocols > IIOP page to confirm whether IIOP is enabled.
    Affected if IIOP protocol is enabled on the affected server instance
  4. Verify T3 protocol is enabled
    Examine the config.xml file for T3 protocol settings or access the WebLogic Administration Console and navigate to the Server > Protocols > T3 page to check if the T3 protocol is enabled.
    Affected if T3 protocol is enabled on the affected server instance
  5. Check network exposure of IIOP and T3 ports
    Identify the IIOP default port (usually 7001 plus offset) and T3 default port (usually 7001 plus offset) in your configuration, then use netstat or similar network tools to determine if these ports are listening on network interfaces accessible from untrusted networks.
    Affected if IIOP or T3 ports are exposed to untrusted network addresses

The environment is affected if Oracle WebLogic Server is installed with a version between 10.3.6.0.0 and 14.1.1.0.0 AND either the IIOP or T3 protocol is enabled and accessible over 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 that addresses CVE-2020-14645, or upgrade to a patched version of WebLogic Server. If immediate patching is not possible, consider restricting network access to IIOP and T3 ports or disabling these protocols if not required.

Recommended fix High confidence

WebLogic Server 14.1.1.x (supported release with latest Critical Patch Updates)

  1. 1. Review the Oracle July 2020 Critical Patch Update (CPU) advisory for CVE-2020-14645
  2. 2. Identify your current WebLogic Server version using the WebLogic Administration Console or by checking the installation directory
  3. 3. For version 10.3.6.0.0: Oracle no longer provides patches for this older line; plan migration to WebLogic Server 12.2.1.x or 14.1.1.x
  4. 4. For version 12.1.3.0.0: Apply the July 2020 CPU patch (or successor patch) if available, or upgrade to WebLogic Server 12.2.1.4.0 with latest CPU applied, or upgrade to 14.1.1.x
  5. 5. For versions 12.2.1.3.0 and 12.2.1.4.0: Apply Oracle Critical Patch Update (July 2020 or later) that addresses this vulnerability
  6. 6. If upgrading to 14.1.1.x is chosen, ensure application compatibility testing is performed before production deployment
  7. 7. After patching or upgrading, verify the IIOP and T3 protocols are secured (restrict network access, enable authentication)
  8. 8. Restart WebLogic Server instances as required by the patch installation
Caveat Upgrading across major version lines (e.g., 12.1.3 to 14.1.1) may require application re-testing for compatibility; review Oracle's upgrade documentation for breaking changes

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

Fix this in Weblogic Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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