dbcve.org
Weblogic ServerApplication · Oracle

CVE-2021-2394

CRITICAL · 9.8 CVSS v3.1 Published 2021-07-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
High EPSS 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 T3, IIOP 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. Attackers can exploit this flaw via T3 or IIOP network protocols without any credentials, achieving complete server takeover. The vulnerability affects versions 10.3.6.0.0 through 14.1.1.0.0 and is rated Critical due to the trivial exploitability and full compromise potential.

MitigationApply Oracle Critical Patch Update (CPU) patches for CVE-2021-2394. As an immediate workaround, restrict network access to T3/IIOP ports or disable 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. Identify WebLogic Server installation and version
    Locate the WebLogic installation directory (typically $ORACLE_HOME or /opt/oracle/middleware) and check the version file: look for 'registry.xml' or 'version.txt' in the wlserver_10.3 or wlserver directory. Alternatively, run: java -jar $ORACLE_HOME/wlserver_10.3/server/lib/weblogic.jar 2>/dev/null | grep -i version
    Affected if The installed version falls within 10.3.6.0.0 through 14.1.1.0.0 (any of the listed versions: 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)
  2. Verify T3 protocol is enabled
    Examine the WebLogic Server startup scripts and configuration files. Check the 'setDomainEnv.sh' or 'startWebLogic.sh' scripts for T3-related JVM arguments (such as -Djava.rmi.server.hostname, -Djavax.rmi.ssl.client.enabled, or T3-specific settings). Also inspect the config.xml file in the domain directory for Network Access Points or Channels configured for T3 protocol
    Affected if T3 protocol is enabled or configured on any network channel/listener in the WebLogic domain configuration
  3. Verify IIOP protocol is enabled
    Inspect the WebLogic domain config.xml file for <IIOP> elements or IIOP-related network channel configurations. Check the Administration Console under 'Servers > YourServer > Protocols > IIOP' to see if IIOP is enabled. Look for iiop:// listeners in the config
    Affected if IIOP protocol is enabled on any server or network channel in the WebLogic domain
  4. Check exposure of T3/IIOP network ports
    Identify the ports configured for T3 (typically 7001 for admin, but varies by domain) and IIOP (typically 7002 or 2809) by reviewing the config.xml or running: netstat -anlp 2>/dev/null | grep -E '7001|7002|2809|8080|9001'. Verify if these ports are accessible from untrusted networks or the internet
    Affected if T3 or IIOP ports are listening on interfaces accessible from untrusted networks or the public internet

The environment is affected if WebLogic Server version is between 10.3.6.0.0 and 14.1.1.0.0 AND either T3 or IIOP 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 Oracle Critical Patch Update (CPU) patches for CVE-2021-2394. As an immediate workaround, restrict network access to T3/IIOP ports or disable these protocols if not required.

Recommended fix High confidence

Oracle WebLogic Server 14.1.1.0.0 or later (or apply July 2021 CPU patch 33452768)

  1. 1. Download and apply Oracle Critical Patch Update (CPU) July 2021 from Oracle Support (Patch 33452768 or later)
  2. 2. For Oracle WebLogic Server 10.3.6.0.0, 12.1.3.0.0, 12.2.1.3.0, 12.2.1.4.0: apply the July 2021 CPU patch or upgrade to 14.1.1.0.0
  3. 3. Alternatively, upgrade directly to Oracle WebLogic Server 14.1.1.0.0 or later which includes the fix
  4. 4. After patching, restart all WebLogic Server instances and managed servers
  5. 5. As an additional mitigation, restrict network access to T3/IIOP protocols by configuring network access controls or firewall rules to limit exposure to trusted networks only
Caveat Upgrade to 14.1.1.x may require application compatibility testing; review Oracle's upgrade documentation for breaking changes between 12.x and 14.x releases

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
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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