dbcve.org
Weblogic ServerApplication · Oracle

CVE-2021-2047

CRITICAL · 9.8 CVSS v3.1 Published 2021-01-20
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 Components). Supported versions that are affected are 10.3.6.0.0, 12.1.3.0.0, and 12.2.1.3.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

Vulnerability in Oracle WebLogic Server Core Components allows unauthenticated remote attackers to achieve remote code execution via specially crafted IIOP or T3 protocol requests. The flaw enables complete server takeover due to insecure deserialization handling in these Oracle-specific network protocols.

MitigationApply Oracle Critical Patch Update (CPU) patches for CVE-2021-2047 to affected WebLogic versions (10.3.6.0.0, 12.1.3.0.0, 12.2.1.3.0). If patching is not immediately feasible, disable or restrict IIOP/T3 protocol access at the network level until patching can be completed.

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

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 installed WebLogic Server version
    Check the Oracle WebLogic inventory or read the version file in the installation directory (such as PRODUCT_HOME/registry.xml or the installation manifest). Alternatively, access the WebLogic Administration Console and check the server version displayed in the About page.
    Affected if The installed version matches exactly 10.3.6.0.0, 12.1.3.0.0, or 12.2.1.3.0.
  2. Verify IIOP protocol is enabled
    Check the WebLogic Server configuration for IIOP settings. In the Administration Console, navigate to Servers > [server name] > Protocols > IIOP. Also check if the IIOP listener port (default 9002) is open and listening on the server.
    Affected if IIOP is enabled and the IIOP listener is active on the affected version.
  3. Verify T3 protocol is enabled
    Check the WebLogic Server configuration for T3 settings. In the Administration Console, navigate to Servers > [server name] > Protocols > T3. Also check if the T3/IIOP listener ports (typically 7001-7003) are accepting T3 connections.
    Affected if T3 is enabled and the server accepts T3 protocol requests on the affected version.
  4. Confirm network exposure of IIOP/T3 ports
    Use netstat, nmap, or equivalent tools to determine which network interfaces the WebLogic IIOP and T3 listener ports are bound to. Verify whether these ports are reachable from untrusted networks.
    Affected if The IIOP or T3 listener ports are bound to routable (non-loopback) network interfaces and accessible from untrusted networks.

The environment is affected if running WebLogic Server version 10.3.6.0.0, 12.1.3.0.0, or 12.2.1.3.0 with either IIOP or T3 protocol enabled and exposed on a network accessible interface.

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-2021-2047 to affected WebLogic versions (10.3.6.0.0, 12.1.3.0.0, 12.2.1.3.0). If patching is not immediately feasible, disable or restrict IIOP/T3 protocol access at the network level until patching can be completed.

Fix this in Weblogic Server Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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