Weblogic ServerApplication · Oracle

CVE-2024-21006

HIGH · 7.5 CVSS v3.1 Published 2024-04-16

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

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 access to critical data or complete access to all Oracle WebLogic Server accessible data. CVSS 3.1 Base Score 7.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).

Technical summary

dbcve analysis · high confidence

Unspecified vulnerability in Oracle WebLogic Server Core component allows unauthenticated attackers with network access via T3 or IIOP protocols to access sensitive data. The vulnerability is easily exploitable and affects versions 12.2.1.4.0 and 14.1.1.0.0 with high confidentiality impact.

MitigationApply Oracle Critical Patch Update addressing CVE-2024-21006; alternatively, restrict or disable T3/IIOP protocol access at the network level until patching can be completed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Weblogic ServerApplication

Affected:= 12.2.1.4.0= 14.1.1.0.0

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify WebLogic Server installation and version

Locate the WebLogic installation directory and check the version. In the installation root, check the file 'registry.xml' or look for 'weblogic.jar' and run: java -cp/weblogic.jar weblogic.version or check PRODUCT_HOME/registry.xml for version information

Affected if Installed version matches 12.2.1.4.0 or 14.1.1.0.0 exactly
Verify T3 protocol is enabled

Check WebLogic server startup scripts (startWebLogic.cmd/sh) and config.xml for T3 protocol configuration. Look for lines containing 't3' or 'enableT3' in the domain config or boot.properties. Alternatively, check the Administration Console under Protocols > Channels

Affected if T3 protocol is explicitly enabled or configured in the WebLogic domain configuration
Verify IIOP protocol is enabled

Check the WebLogic Administration Console under Services > IIOP, or inspect the config.xml file for <iiop> or <iiop-configuration> elements within the server definition

Affected if IIOP is enabled in the server configuration (iiop-enabled set to true)
Confirm network exposure of T3/IIOP listeners

Review network listener configuration in config.xml or use WebLogic Administration Console to check which network addresses and ports the servers bind to. Verify if the Listen Address is set to a public IP or 0.0.0.0 rather than localhost only

Affected if T3 or IIOP listeners are bound to an externally accessible network address (0.0.0.0 or public IP)

A user is affected if they run WebLogic Server version 12.2.1.4.0 or 14.1.1.0.0 with T3 or IIOP protocols enabled and exposed to network access.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Apply Oracle Critical Patch Update addressing CVE-2024-21006; alternatively, restrict or disable T3/IIOP protocol access at the network level until patching can be completed.

Recommended fix High confidence

Apply Oracle CPU patch for CVE-2024-21006 (January 2024 or later)

1. Identify the current Oracle WebLogic Server version by checking the installation (typically in the Oracle_Home directory or using the WebLogic Administration Console)
2. Navigate to Oracle's Critical Patch Updates advisory page (.oracle.com/security-alerts) and locate the January 2024 CPU or subsequent update that addresses CVE-2024-21006
3. Download the appropriate WebLogic Server patch for your version (12.2.1.4.0 or 14.1.1.0.0) from Oracle Support (support.oracle.com) using the Patch ID specified in the advisory
4. Apply the patch using Oracle's Smart Update (OPatch) utility: opatch apply <patch_directory>
5. Restart all WebLogic Server instances and Node Managers to ensure the patch takes effect
6. Verify the patch was applied successfully by checking the WebLogic version and confirming the patch ID is listed in the inventory (opatch lsinventory)
7. If immediate patching is not possible, temporarily restrict network access to T3/IIOP protocols by configuring network ACLs or firewall rules to limit exposure

Caveat Patches typically have minimal impact but should be tested in non-production environment first; some patches may require domain reconfiguration

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
Testing12.0 h
Review / QA4.0 h

28.0 hours of engineering $4,760

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

www.oracle.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-21006 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2024-21006?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 7.5 High

Exploit likelihood EPSS, next 30 days 7.9%

Affects: Weblogic Server

Remediation

A high-priority fix

Fix this in Weblogic Server 28 hrs · Moderate

Typical engagement from $4,760

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2024-21006 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References