dbcve.org
Weblogic ServerApplication · Oracle

CVE-2024-21260

HIGH · 7.5 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 →
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.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

Oracle WebLogic Server contains a vulnerability in the Core component that allows unauthenticated remote attackers to cause a complete denial of service via specially crafted T3 or IIOP network protocol requests. The attack requires network access to the WebLogic ports handling these protocols and results in server hang or repeatable crashes.

MitigationApply Oracle Critical Patch Update (CPU) patches for CVE-2024-21260 to affected WebLogic versions 12.2.1.4.0 and 14.1.1.0.0. Consider restricting network access to T3/IIOP ports if patching cannot be performed immediately.

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
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 installation and version
    Locate the WebLogic installation directory and check the version file or use the WebLogic Administration Console to confirm the installed version. Common paths include the inventory file or the weblogic.Server binary version information.
    Affected if The installed version matches 12.2.1.4.0 or 14.1.1.0.0 exactly.
  2. Determine if T3 protocol is enabled
    Check the WebLogic Server configuration for T3 protocol listeners. This is typically configured in the Administration Console under Servers > [ServerName] > Protocols > T3, or by reviewing the config.xml file for <t3-enabled> elements and associated port bindings.
    Affected if T3 protocol is enabled and listening on a network-accessible port (commonly port 7001 or custom configured).
  3. Determine if IIOP protocol is enabled
    Check the WebLogic Server configuration for IIOP protocol listeners. This is typically configured in the Administration Console under Servers > [ServerName] > Protocols > IIOP, or by reviewing the config.xml file for <iiop-enabled> elements and associated port bindings.
    Affected if IIOP protocol is enabled and listening on a network-accessible port (commonly port 28001 or custom configured).
  4. Assess network exposure of T3/IIOP ports
    Review firewall rules, network ACLs, or cloud security groups to determine if the T3 and IIOP listening ports are accessible from untrusted network segments or the public internet.
    Affected if The T3 or IIOP ports are exposed to untrusted network locations without adequate access controls.

A user is affected if they run Oracle WebLogic Server version 12.2.1.4.0 or 14.1.1.0.0 with T3 or IIOP protocols enabled and network-accessible to 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Update (CPU) patches for CVE-2024-21260 to affected WebLogic versions 12.2.1.4.0 and 14.1.1.0.0. Consider restricting network access to T3/IIOP ports if patching cannot be performed immediately.

Recommended fix High confidence

WebLogic Server 12.2.1.4.0 with October 2024 CPU or later; WebLogic Server 14.1.1.0.0 with October 2024 CPU or later

  1. 1. Apply Oracle Critical Patch Update (CPU) October 2024, which contains the fix for CVE-2024-21260
  2. 2. Download and install the patch from Oracle Support (patch update for WebLogic Server)
  3. 3. For WebLogic Server 12.2.1.4.0: Upgrade to version 12.2.1.4.0 with October 2024 CPU applied (or later quarterly patch)
  4. 4. For WebLogic Server 14.1.1.0.0: Upgrade to version 14.1.1.0.0 with October 2024 CPU applied (or later quarterly patch)
  5. 5. Restart all WebLogic Server instances after applying the patch
  6. 6. Verify the patch was applied successfully by checking the WebLogic Server version and patch inventory
Caveat Oracle CPU patches typically have minimal breaking changes but should be tested in non-production environment first; ensure compatibility with existing applications and JDK version

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

Fix this in Weblogic Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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