dbcve.org
Weblogic ServerApplication · Oracle

CVE-2023-21964

HIGH · 7.5 CVSS v3.1 Published 2023-04-18
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 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 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

Unauthenticated remote denial of service vulnerability in Oracle WebLogic Server's Core component. Exploitable via the T3 protocol network vector, allowing attackers to cause the server to hang or crash repeatedly without authentication.

MitigationApply Oracle Critical Patch Update (CPU) containing the fix for CVE-2023-21964. If immediate patching is not feasible, restrict or disable T3/IIOP network protocols and limit exposure to trusted networks only.

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.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 version
    Check the installed WebLogic version by inspecting the inventory file, registry, or product directory. Typical paths include the Oracle inventory file (inventory.xml) or the WebLogic installation directory structure containing the version info.
    Affected if Installed version matches 12.2.1.3.0, 12.2.1.4.0, or 14.1.1.0.0
  2. Confirm T3 protocol is enabled
    Examine the WebLogic configuration (config.xml) or the administration console to determine if the T3 network protocol is enabled. T3 is enabled by default but should be checked in the server's network channel or channel configuration settings.
    Affected if T3 protocol is enabled and listening on a network port (default port 7001)
  3. Verify network exposure of T3 port
    Determine if the T3 port is accessible from untrusted or external networks. Check firewall rules, network ACLs, and whether the server is directly exposed to the internet or untrusted users.
    Affected if T3 port is reachable from untrusted networks or the internet without proper network segmentation or filtering

A user is affected if they run a vulnerable WebLogic Server version (12.2.1.3.0, 12.2.1.4.0, or 14.1.1.0.0) with T3 protocol enabled and exposed to untrusted network access.

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) containing the fix for CVE-2023-21964. If immediate patching is not feasible, restrict or disable T3/IIOP network protocols and limit exposure to trusted networks only.

Recommended fix Moderate confidence

Apply Oracle Critical Patch Update (CPU) - contact Oracle support for specific patch number for your version

  1. Check Oracle Critical Patch Updates (CPUs) for April 2023 or later for CVE-2023-21964
  2. Apply the latest Oracle Critical Patch Update that includes the fix for this vulnerability
  3. Alternatively, if no patch is immediately available, restrict T3 protocol access by configuring network access controls to limit which hosts can connect to the WebLogic Server T3 port
  4. Verify that T3/IIOP protocols are only exposed to trusted networks

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
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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