dbcve.org
Weblogic ServerApplication · Oracle

CVE-2022-21306

CRITICAL · 9.8 CVSS v3.1 Published 2022-01-19
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 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 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 vulnerability in its Core component that allows unauthenticated remote attackers to achieve complete server takeover via the T3 protocol. The T3 protocol is Oracle's proprietary protocol used for communication between WebLogic Server instances and clients. This is a remote code execution vulnerability with CVSS 9.8, requiring only network access and no authentication.

MitigationApply the Oracle Critical Patch Update (CPU) that includes the fix for CVE-2022-21306 to all affected WebLogic Server installations. If immediate patching is not possible, consider restricting network access to T3/IIOP ports or disabling the T3 protocol 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:= 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
    Locate the WebLogic Server installation directory. Common paths include $ORACLE_HOME/wlserver or /Oracle/Middleware/wlserver. Check for the existence of the 'wlserver' directory and the 'modules' or 'server/lib' subdirectories containing WebLogic JAR files.
    Affected if WebLogic Server is not installed on the system.
  2. Determine installed WebLogic Server version
    Check the WebLogic version by examining the 'registry.xml' file in the installation directory, or run: java -jar wlserver/server/lib/weblogic.jar -version. Alternatively, check the 'product.properties' or 'version.info' files typically found in the wlserver directory.
    Affected if The installed version matches exactly 12.1.3.0.0, 12.2.1.3.0, 12.2.1.4.0, or 14.1.1.0.0.
  3. Verify T3 protocol is enabled
    Inspect the WebLogic Server configuration files (config.xml) in the domain directory for T3 protocol configuration. Check for '<network-access-point>' entries with T3, or examine the Administration Console settings under Protocols > T3. The T3 protocol is typically enabled by default on port 7001.
    Affected if T3 protocol is enabled and listening on any network interface.
  4. Confirm network exposure of T3/IIOP ports
    Review firewall rules and WebLogic network configuration to determine if T3 ports (default 7001) or IIOP ports (default 7002) are exposed to untrusted networks. Use 'netstat -an | grep 7001' or 'netstat -an | grep 7002' to check listening ports.
    Affected if T3 or IIOP ports are bound to 0.0.0.0 or an externally accessible IP address.

A user is affected if they have WebLogic Server version 12.1.3.0.0, 12.2.1.3.0, 12.2.1.4.0, or 14.1.1.0.0 installed with T3 protocol enabled and exposed on 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 the Oracle Critical Patch Update (CPU) that includes the fix for CVE-2022-21306 to all affected WebLogic Server installations. If immediate patching is not possible, consider restricting network access to T3/IIOP ports or disabling the T3 protocol until patching can be completed.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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