dbcve.org
Weblogic ServerApplication · Oracle

CVE-2020-14687

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 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

Unauthenticated remote code execution vulnerability in Oracle WebLogic Server's core component, exploitable via T3 and IIOP protocols. Allows complete takeover of the WebLogic Server without any credentials.

MitigationApply Oracle Critical Patch Update (CPU) or specific patch for CVE-2020-14687. Alternatively, disable T3/IIOP protocols if not required and implement network segmentation to limit exposure.

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 if Oracle WebLogic Server is installed
    Check for WebLogic installation directories (typically $ORACLE_HOME/wlserver or $MW_HOME/wlserver) or look for WebLogic processes running: ps -ef | grep -i weblogic or check Windows services for WebLogic entries
    Affected if WebLogic Server process or installation directory is found on the system
  2. Determine the installed WebLogic version
    Check the installation manifest or version file. Common locations: <WL_HOME>/inventory/ContentsXML/compon.xml, or look for VERSION.TXT in the installation directory. You can also query the Admin Console or check the log files for version information
    Affected if Installed version matches 12.2.1.3.0, 12.2.1.4.0, or 14.1.1.0.0 exactly
  3. Check if T3 protocol is enabled
    Review the WebLogic Server configuration in the Admin Console under Servers > [Server Name] > Protocols, or check the config.xml file for <server>-<protocols>-<t3-enabled> settings. T3 is enabled by default on managed servers and Admin Server
    Affected if T3 protocol is enabled and exposed on the network
  4. Check if IIOP protocol is enabled
    Review the WebLogic Server configuration in the Admin Console under Servers > [Server Name] > Protocols > IIOP, or check config.xml for <iiop-enabled> settings. IIOP is enabled by default on managed servers
    Affected if IIOP protocol is enabled and exposed on the network
  5. Assess network exposure of WebLogic ports
    Identify listening ports (default: 7001 for Admin Console, 7002 for SSL, managed server ports typically 8001+). Check if these ports are accessible from untrusted networks using tools like netstat, nmap, or firewall rules. T3 typically uses the Admin port, IIOP uses port 7002 by default
    Affected if WebLogic ports (T3/IIOP) are accessible from untrusted or external network segments

The environment is affected if Oracle WebLogic Server versions 12.2.1.3.0, 12.2.1.4.0, or 14.1.1.0.0 are installed AND either T3 or IIOP protocol is enabled AND exposed to network 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.

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

Apply Oracle Critical Patch Update (CPU) or specific patch for CVE-2020-14687. Alternatively, disable T3/IIOP protocols if not required and implement network segmentation to limit exposure.

Recommended fix High confidence

Oracle WebLogic Server 14.1.1.1.0 or later (14.x line)

  1. 1. Backup your current Oracle WebLogic Server installation and all applications.
  2. 2. Download Oracle WebLogic Server 14.1.1.1.0 (or latest 14.x version) from Oracle eDelivery or My Oracle Support.
  3. 3. Uninstall the current WebLogic Server 14.1.1.0.0 installation.
  4. 4. Install WebLogic Server 14.1.1.1.0 following the Oracle installation documentation.
  5. 5. Redeploy your applications to the upgraded WebLogic Server instance.
  6. 6. Verify that all applications are functioning correctly after the upgrade.
  7. 7. Verify that the IIOP and T3 protocols are properly secured or restricted if not required.
Caveat Review Oracle WebLogic Server 14.1.1.1.0 compatibility documentation as there may be API or configuration changes affecting legacy applications; thorough testing in non-production environment recommended before production deployment

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

Fix this in Weblogic Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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