dbcve.org
Weblogic ServerApplication · Oracle

CVE-2022-21441

HIGH · 7.5 CVSS v3.1 Published 2022-04-19
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/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

Denial of service vulnerability in Oracle WebLogic Server's Core component affecting versions 12.2.1.3.0, 12.2.1.4.0, and 14.1.1.0.0. Exploitable remotely via T3/IIOP protocols without authentication, allowing attackers to cause complete server hang or repeatable crashes.

MitigationApply Oracle Critical Patch Update (CPU) containing the fix for CVE-2022-21441. As an interim control, restrict network access to T3/IIOP ports (typically 7001/7002) to trusted sources 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 Server version by inspecting the installation directory or using the WebLogic Administration Console. Look for the version file in the Oracle home directory or check the console's 'About' page.
    Affected if The installed version matches exactly 12.2.1.3.0, 12.2.1.4.0, or 14.1.1.0.0
  2. Check if T3 protocol is enabled
    Review WebLogic Server configuration for T3 protocol listeners. In the Administration Console, navigate to the Servers configuration and inspect the Protocol settings, or check the config.xml file for <t3-enabled> settings.
    Affected if T3 protocol is enabled and listening on the server (typically ports 7001/7002)
  3. Check if IIOP protocol is enabled
    Review WebLogic Server configuration for IIOP protocol listeners. In the Administration Console, navigate to the Servers configuration and inspect the IIOP settings, or check the config.xml file for <iiop-enabled> settings.
    Affected if IIOP protocol is enabled and listening on the server
  4. Verify network accessibility of T3/IIOP ports
    Check firewall rules, network ACLs, or WebLogic network channel configurations to determine if ports 7001 and 7002 (or custom T3/IIOP ports) are accessible from untrusted network segments.
    Affected if T3 or IIOP ports are exposed to untrusted network access without proper filtering

A user is affected if they run WebLogic Server version 12.2.1.3.0, 12.2.1.4.0, or 14.1.1.0.0 with T3 or IIOP protocols enabled and accessible to untrusted networks.

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-2022-21441. As an interim control, restrict network access to T3/IIOP ports (typically 7001/7002) to trusted sources only.

Recommended fix Moderate confidence

Oracle WebLogic Server 12.2.1.3.0, 12.2.1.4.0, and 14.1.1.0.0 should be updated to their latest respective versions with the April 2022 CPU or later patches applied

  1. Review the Oracle Critical Patch Update April 2022 for the CVE-2022-21441 patch specific to WebLogic Server
  2. Download and apply the April 2022 Critical Patch Update (CPU) or a subsequent patch that addresses CVE-2022-21441
  3. For WebLogic Server 12.2.1.3.0: Apply the quarterly patch set update that includes the fix, typically requires upgrading to a later PSU version
  4. For WebLogic Server 12.2.1.4.0: Apply the quarterly patch set update that includes the fix
  5. For WebLogic Server 14.1.1.0.0: Apply the quarterly patch set update that includes the fix
  6. Restart the WebLogic Server after applying the patch
  7. Verify the patch was successfully applied by checking the patch inventory and testing T3/IIOP functionality
Caveat Review Oracle's patch compatibility documentation; some patches may require specific earlier prerequisite patches; test thoroughly in non-production environment before applying to production

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
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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