dbcve.org
Weblogic ServerApplication · Oracle

CVE-2024-21216

CRITICAL · 9.8 CVSS v3.1 Published 2024-10-15
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 Core component allows attackers with network access via T3 or IIOP protocols to completely take over affected WebLogic Server instances. The vulnerability affects versions 12.2.1.4.0 and 14.1.1.0.0 and requires no authentication or user interaction.

MitigationApply the Oracle Critical Patch Update addressing CVE-2024-21216 immediately. As an interim measure, restrict or disable T3/IIOP network protocols if not required for business operations, and ensure WebLogic admin ports are not exposed to untrusted networks.

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 version
    Check the installed Oracle WebLogic Server version by reviewing the installation directory or using the WebLogic Administration Console. The version is typically found in the product inventory or can be retrieved via the weblogic.version system property.
    Affected if Installed version equals 12.2.1.4.0 or 14.1.1.0.0 exactly
  2. Verify T3 protocol is enabled
    Review the WebLogic Server configuration files (config.xml) or access the Administration Console to check whether the T3 protocol listener is enabled. T3 is typically enabled on the default admin port (7001) unless explicitly disabled.
    Affected if T3 protocol is enabled and accessible on any listening port
  3. Verify IIOP protocol is enabled
    Review the WebLogic Server configuration to determine if the IIOP protocol service is enabled. Check the config.xml for IIOP settings or verify via the Administration Console under the Servers > Protocol settings.
    Affected if IIOP protocol is enabled and accessible on any listening port
  4. Confirm network exposure of admin ports
    Identify all ports running WebLogic administration services and verify whether they are exposed to untrusted networks. Use netstat or port scanning tools to list open ports and determine if admin ports (typically 7001 for T3, 7002 for IIOP) are reachable from external IPs.
    Affected if T3 or IIOP ports are reachable from untrusted or public networks

A system is affected if it runs WebLogic Server version 12.2.1.4.0 or 14.1.1.0.0 with T3 or IIOP protocols enabled and accessible from the network where unauthenticated attackers can reach these services.

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 the Oracle Critical Patch Update addressing CVE-2024-21216 immediately. As an interim measure, restrict or disable T3/IIOP network protocols if not required for business operations, and ensure WebLogic admin ports are not exposed to untrusted networks.

Recommended fix Moderate confidence

Oracle Critical Patch Update (CPU) containing CVE-2024-21216 fix, or Oracle WebLogic Server 12.2.1.4.x/14.1.1.0.x with incorporated fix

  1. Check Oracle's Critical Patch Updates (CPUs) for the patch addressing CVE-2024-21216. The fix is typically delivered via Oracle CPU (Critical Patch Update).
  2. Apply the latest Oracle Critical Patch Update that includes the fix for this vulnerability. For 2024, check the July 2024 CPU or subsequent updates.
  3. Alternatively, if Oracle has released a newer version of WebLogic Server that includes the fix, upgrade to that version.
  4. After applying the patch, verify the T3 and IIOP protocols are properly secured if not needed, or ensure network access is restricted to legitimate users only.
  5. Restart the WebLogic Server as required by the patch installation process.
  6. Validate the patch was applied correctly by checking the WebLogic Server version and confirming the vulnerability is resolved.
Caveat Oracle CPU patches are generally cumulative and include all prior fixes; review the CPU advisory for any special installation instructions or known issues

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

Fix this in Weblogic Server Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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