dbcve.org
Weblogic ServerApplication · Oracle

CVE-2021-2378

HIGH · 7.5 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 →
84/100
Remediation priority · High
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 unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle WebLogic Server. CVSS 3.1 Base Score 7.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 vulnerability in its Core component allowing unauthenticated remote attackers to cause denial of service via T3 or IIOP network protocols. The attack requires no authentication, has low complexity, and results in complete server availability loss.

MitigationApply Oracle's October 2021 Critical Patch Update (CPU) containing the security fix for CVE-2021-2378, or upgrade to a patched version of WebLogic Server. As an interim control, restrict or disable T3/IIOP protocols at the network level 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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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
    Locate WebLogic installation directory: check for /Oracle/Middleware/, /u01/oracle/, or similar paths. Look for the 'bea' or 'oracle' directories containing 'wlserver' or 'coherence' subdirectories.
    Affected if WebLogic Server is installed on the system
  2. Determine WebLogic Server version
    Check the version file in the installation directory, typically at <WEBLOGIC_HOME>/registry.xml or look at the 'Inventory.xml' in the oracle_common directory. Alternatively, check the product version in the WebLogic Administration Console under 'Environment' > 'Servers' or examine the startup logs for version information.
    Affected if 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 exactly
  3. Check if T3 protocol is enabled
    In WebLogic Administration Console, go to 'Environment' > 'Servers' > select each server > 'Protocols' > 'General'. Look for 'Enable T3' setting. Alternatively, search configuration files (config.xml) for '<network-access-point>' entries containing 'T3' or check for system properties -Dt3.enabled or -Dweblogic.rjvm.enabledprotocols including T3.
    Affected if T3 protocol is enabled on any managed server or admin server listening on the network
  4. Check if IIOP protocol is enabled
    In WebLogic Administration Console, go to 'Environment' > 'Servers' > select each server > 'Protocols' > 'IIOP'. Look for 'Enable IIOP' setting. Alternatively, search config.xml for '<iiop-enabled>true</iiop-enabled>' or check for -Diiop.enabled system property.
    Affected if IIOP protocol is enabled on any managed server accessible over the network
  5. Verify network exposure of T3/IIOP listeners
    Review network configurations and firewall rules to determine if T3 (port 7001 default) or IIOP (port 7002 default) ports are exposed to untrusted networks. Use 'netstat -an | grep -E '700[12]'' to identify listening ports, and verify access control lists permit external access.
    Affected if T3 or IIOP ports are reachable from untrusted network segments or the internet

You are affected if WebLogic Server version is exactly 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 AND either T3 or IIOP protocol is enabled and accessible from 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle's October 2021 Critical Patch Update (CPU) containing the security fix for CVE-2021-2378, or upgrade to a patched version of WebLogic Server. As an interim control, restrict or disable T3/IIOP protocols at the network level if not required.

Fix this in Weblogic Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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