dbcve.org
Weblogic ServerApplication · Oracle

CVE-2020-2884

CRITICAL · 9.8 CVSS v3.1 Published 2020-04-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 and 12.2.1.4.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.0 Base Score 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/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 deserialization vulnerability in Oracle WebLogic Server's Core component affecting versions 10.3.6, 12.1.3, 12.2.1.3, and 12.2.1.4. Allows unauthenticated remote code execution via IIOP or T3 network protocols, enabling complete server takeover.

MitigationApply Oracle Critical Patch Update (CPU) containing the security fix for CVE-2020-2884, or disable IIOP/T3 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:= 10.3.6.0.0= 12.1.3.0.0= 12.2.1.3.0= 12.2.1.4.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 version
    Locate the WebLogic installation and check the version. In the Oracle inventory (or ORACLE_HOME/oraInst.loc), or inspect the file $ORACLE_HOME/wlserver/server/lib/weblogic.jar for version metadata. Alternatively, access the WebLogic Admin Console and check the Domain > General > Version information.
    Affected if The installed version matches 10.3.6.0.0, 12.1.3.0.0, 12.2.1.3.0, or 12.2.1.4.0 exactly.
  2. Verify IIOP protocol is enabled
    Examine the WebLogic domain config.xml file (located in $DOMAIN_HOME/config/config.xml). Search for <iiop> or <iiop-system-enabled> elements. Alternatively, in the Admin Console navigate to Domain > Protocols > IIOP to confirm whether IIOP is enabled.
    Affected if IIOP is enabled (iiop-system-enabled is set to true or the iiop MBean is configured without restrictions).
  3. Verify T3 protocol is enabled
    Examine the WebLogic domain config.xml for <network-access-point> entries where the protocol is T3, or check if the default Admin Server T3 listener is active. In the Admin Console, inspect the Servers > [ServerName] > Protocols > T3 page.
    Affected if T3 protocol is enabled and accessible (not disabled or restricted to localhost).
  4. Check network exposure of IIOP/T3 ports
    Identify the ports configured for IIOP (default 7001-7002 for admin, or dedicated IIOP ports) and T3 (default 7001 for admin). Review firewall rules, load balancer configurations, or cloud security groups to determine if these ports are reachable from untrusted networks.
    Affected if The IIOP or T3 listening ports are exposed to networks outside the trusted internal environment (e.g., the internet or DMZ).

The environment is affected if WebLogic Server version is exactly 10.3.6.0.0, 12.1.3.0.0, 12.2.1.3.0, or 12.2.1.4.0, AND either the IIOP or T3 protocol is enabled, AND the affected ports are network-accessible from untrusted sources.

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) containing the security fix for CVE-2020-2884, or disable IIOP/T3 protocols if not required, and implement network segmentation to limit exposure.

Recommended fix High confidence

Oracle WebLogic Server 12.2.1.4.0.200414 (April 2020 CPU) or later; or upgrade to latest 14.1.1.0.0

  1. Apply Oracle Critical Patch Update (CPU) April 2020, which includes the fix for CVE-2020-2884
  2. For WebLogic 10.3.6.0.0: Apply patch 31241087 or upgrade to 10.3.6.0.200414 or later
  3. For WebLogic 12.1.3.0.0: Apply patch 31241087 or upgrade to 12.1.3.0.200414 or later
  4. For WebLogic 12.2.1.3.0: Apply patch 31241087 or upgrade to 12.2.1.3.0.200414 or later
  5. For WebLogic 12.2.1.4.0: Apply patch 31241087 or upgrade to 12.2.1.4.0.200414 or later
  6. Alternatively, upgrade to WebLogic 14.1.1.0.0 (latest permanent release) which includes all security fixes
  7. After patching, restart all WebLogic Server instances to apply the fix
  8. Verify the patch was applied successfully by checking the Oracle WebLogic Server version and applied patches
Caveat Upgrade within same major version typically low risk; however, ensure compatibility with deployed applications before upgrading major versions like to 14.x

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
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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