dbcve.org
Weblogic ServerApplication · Oracle

CVE-2024-21181

CRITICAL · 9.8 CVSS v3.1 Published 2024-07-16
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.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

Unauthenticated remote code execution vulnerability in Oracle WebLogic Server's core component, exploitable via T3 and IIOP network protocols. Successful exploitation grants attackers complete takeover of the affected WebLogic Server instance.

MitigationApply Oracle Critical Patch Update (CPU) or superseding patches for CVE-2024-21181 to affected versions 12.2.1.4.0 and 14.1.1.0.0. As an interim control, restrict network access to T3/IIOP ports from untrusted sources.

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.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 WebLogic installation directory. Common paths: $ORACLE_HOME/wlserver, $MW_HOME/wlserver, or C:\Oracle\Middleware\wlserver. Check for existence of weblogic.Server class or wlserver_*.jar files.
    Affected if WebLogic Server is not installed on the system.
  2. Determine WebLogic Server version
    Check the version.properties file in the wlserver directory, or run: java -jar wlserver_*.jar -invoker -printVersion. Also check the patch inventory via $ORACLE_HOME/OPatch/opatch lsinventory.
    Affected if Installed version exactly matches 12.2.1.4.0 or 14.1.1.0.0.
  3. Identify T3 protocol listeners
    Review the WebLogic Server configuration in the Administration Console under Servers > [server name] > Protocols > T3, or inspect the config.xml file for <t3-enabled>true</t3-enabled> entries. Default T3 port is 7001.
    Affected if T3 protocol is enabled and exposed on a network-accessible port.
  4. Identify IIOP protocol listeners
    Review the Administration Console under Servers > [server name] > Protocols > IIOP, or inspect config.xml for <iiop-enabled>true</iiop-enabled> entries. Default IIOP port is 7002.
    Affected if IIOP protocol is enabled and exposed on a network-accessible port.
  5. Check network exposure of WebLogic ports
    Identify all listening ports associated with WebLogic processes using netstat -an | grep -E '7001|7002' or PowerShell Get-NetTCPConnection. Verify if these ports are bound to 0.0.0.0 or accessible from untrusted networks.
    Affected if T3 or IIOP ports are listening on interfaces accessible from untrusted networks.

The environment is affected if WebLogic Server version 12.2.1.4.0 or 14.1.1.0.0 is installed AND either the T3 or IIOP protocol is enabled and exposed to network attackers.

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 Critical Patch Update (CPU) or superseding patches for CVE-2024-21181 to affected versions 12.2.1.4.0 and 14.1.1.0.0. As an interim control, restrict network access to T3/IIOP ports from untrusted sources.

Fix this in Weblogic Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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