dbcve.org
Weblogic ServerApplication · Oracle

CVE-2021-2382

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
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: Security). 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

Oracle WebLogic Server contains a critical security vulnerability in its Security component that allows unauthenticated remote attackers to achieve complete server takeover via T3 or IIOP network protocols. The vulnerability affects versions 10.3.6.0.0 through 14.1.1.0.0 and is easily exploitable without any authentication, providing full confidentiality, integrity, and availability compromise.

MitigationApply Oracle Critical Patch Updates (CPU) addressing CVE-2021-2382 or restrict/.disable T3 and IIOP network protocols if patching cannot be performed immediately; network segmentation can reduce attack surface.

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 (common paths: $ORACLE_HOME/wlserver, /u01/oracle/weblogic, C:\Oracle\Middleware). Check the registry file (registry.xml) or use WebLogic Scripting Tool (WLST): java weblogic.WLST -printStackTraces -execfile getVersion.py where the script contains 'print productVersion' and 'print serverVersion'. Alternatively, check the manifest file in wlserver/server/lib/weblogic.jar or the bin/setDomainEnv.sh script for version indicators.
    Affected if The installed version falls within 10.3.6.0.0 through 14.1.1.1.0.0 (note: versions before 14.1.1.0.0 are affected, 14.1.1.0.0 and above are NOT affected). Compare your version to these ranges.
  2. Confirm T3 protocol is enabled
    Examine the WebLogic domain config.xml file (located in $DOMAIN_HOME/config/config.xml). Look for <network-access-point> entries with <protocol>t3</protocol> or check for <iiop-enabled>true</iiop-enabled> in the <server> section. Alternatively, log into the WebLogic Administration Console, navigate to the server's Configuration > General tab and check the 'Enable T3' checkbox status. Default T3 port is 7001.
    Affected if T3 protocol is enabled on any server instance (the vulnerability is exploitable ONLY when T3 is enabled and accessible over the network).
  3. Confirm IIOP protocol is enabled
    Examine the WebLogic domain config.xml file for <iiop-enabled>true</iiop-enabled> under <server> elements, or check via the Administration Console under Server > Configuration > IIOP. Default IIOP ports are 7001/7002 (same as T3).
    Affected if IIOP protocol is enabled on any server instance (the vulnerability is exploitable ONLY when IIOP is enabled and accessible over the network).
  4. Verify network exposure of WebLogic ports
    Check which network interfaces the WebLogic servers are bound to by examining the <listen-address> setting in config.xml or the Server > Configuration > General > Listen Address in the console. Use 'netstat -an | grep 7001' or 'ss -tlnp | grep 7001' to verify if ports 7001 (default T3/IIOP) or configured custom ports are listening on external interfaces (0.0.0.0) rather than localhost only.
    Affected if WebLogic T3/IIOP ports are exposed to untrusted networks (the vulnerability requires network access to T3 or IIOP protocols).

You are affected if your 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 the WebLogic ports are accessible from a network where untrusted attackers could send requests.

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 Updates (CPU) addressing CVE-2021-2382 or restrict/.disable T3 and IIOP network protocols if patching cannot be performed immediately; network segmentation can reduce attack surface.

Recommended fix High confidence

Oracle WebLogic Server 14.1.1.0.0 or later with April 2021 CPU applied

  1. 1. Download Oracle Critical Patch Update (CPU) April 2021 or later from Oracle Support (requires Oracle account)
  2. 2. Review the README.txt for CVE-2021-2382 and associated patch numbers for your specific WebLogic Server version
  3. 3. Download the applicable patch (e.g., patch number for your version) using Oracle Opatch utility
  4. 4. Stop all WebLogic Server processes and Node Manager
  5. 5. Back up the existing Oracle WebLogic Server installation directory
  6. 6. Apply the patch using: opatch apply <patch_directory>
  7. 7. Verify patch installation success with: opatch lsinventory
  8. 8. Restart WebLogic Server processes and Node Manager
Caveat Apply CPU patch on same version; if upgrading to 14.x, test application compatibility thoroughly as API differences may exist

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

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