dbcve.org
Weblogic ServerApplication · Oracle

CVE-2024-21007

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 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 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 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 an access control vulnerability in its Core component affecting versions 12.2.1.4.0 and 14.1.1.0.0. The flaw is exploitable via T3 and IIOP protocols by unauthenticated remote attackers, potentially allowing unauthorized access to critical or all accessible data.

MitigationApply the relevant Oracle Critical Patch Update (CPU) for CVE-2024-21007 to all affected WebLogic Server instances. As an interim measure, restrict network access to T3/IIOP ports or disable these protocols if not required.

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
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? 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 (typically under Oracle Middleware or Oracle Home). Check the version using the WebLogic Administration Console (accessible via HTTP on the configured admin port, usually 7001) or by inspecting the registry file: <WebLogic_Home>/registry.xml or the installation inventory. Alternatively, check the product version in the WebLogic startup logs.
    Affected if The installed version is exactly 12.2.1.4.0 or 14.1.1.0.0.
  2. Confirm T3 protocol is enabled
    Log into the WebLogic Administration Console. Navigate to the server configuration (Server -> <ServerName> -> Protocols). Verify that the T3 protocol is enabled. T3 typically listens on the same port as the administration port (default 7001). You can also inspect the config.xml file in the domain configuration directory for <protocols><t3>...</t3></protocols>.
    Affected if T3 protocol is enabled on the WebLogic Server (this is the default configuration).
  3. Confirm IIOP protocol is enabled
    Log into the WebLogic Administration Console. Navigate to the server configuration (Server -> <ServerName> -> Protocols -> IIOP). Verify that the IIOP protocol is enabled. IIOP typically listens on port 7002 by default. You can also inspect the config.xml file in the domain configuration directory for <protocols><iiop>...</iiop></protocols>.
    Affected if IIOP protocol is enabled on the WebLogic Server (this is the default configuration).
  4. Check network exposure of T3/IIOP ports
    Identify the ports configured for T3 and IIOP protocols (default 7001 and 7002 respectively). Use network scanning tools (such as netstat, nmap, or equivalent) to determine if these ports are accessible from untrusted networks. Example command: netstat -an | grep -E '7001|7002' or nmap -p 7001,7002 <target>
    Affected if Port 7001 (T3) or port 7002 (IIOP) are exposed to untrusted or external network segments without proper firewall filtering.

You are affected if your WebLogic Server version is exactly 12.2.1.4.0 or 14.1.1.0.0 AND the T3 or IIOP protocols are enabled (default) AND these ports are network-accessible to untrusted parties.

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 the relevant Oracle Critical Patch Update (CPU) for CVE-2024-21007 to all affected WebLogic Server instances. As an interim measure, restrict network access to T3/IIOP ports or disable these protocols if not required.

Fix this in Weblogic Server Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,660
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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