dbcve.org
Weblogic ServerApplication · Oracle

CVE-2024-20931

HIGH · 7.5 CVSS v3.1 Published 2024-02-17
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
High EPSS 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

Unauthenticated remote vulnerability in Oracle WebLogic Server's Core component allows attackers with network access via T3 or IIOP protocols to compromise the server. Successful exploitation grants unauthorized access to critical data or complete access to all WebLogic Server accessible data.

MitigationRestrict network access to T3 and IIOP protocols (e.g., via firewall rules or WebLogic network channel configuration) and apply the Oracle patch when available.

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 installed WebLogic Server version
    Locate the Oracle WebLogic Server installation directory and check the version file (typically in the registry or about page). In WebLogic console, navigate to 'Server' > 'Summary of Servers' or check the 'About WebLogic Server' page. Alternatively, check the file: MW_HOME/wlserver_*/server/lib/weblogic.jar version manifest, or run: java -jar $MW_HOME/wlserver_*/server/lib/weblogic.jar -verbose
    Affected if The installed version is exactly 12.2.1.4.0 or exactly 14.1.1.0.0
  2. Confirm T3 protocol is enabled and accessible
    Check WebLogic Server network channel configuration. In WebLogic Administration Console, go to 'Servers' > 'YourServer' > 'Protocols' > 'General'. Verify if T3 protocol is enabled. Also check if the server listens on default T3 ports (typically 7001 for admin, 7002-700x for managed servers). Use netstat or similar to confirm the server is accepting T3 connections on configured ports.
    Affected if T3 protocol is enabled and the WebLogic ports accepting T3 traffic are reachable from untrusted networks
  3. Confirm IIOP protocol is enabled and accessible
    Check WebLogic Server IIOP configuration. In WebLogic Administration Console, navigate to 'Servers' > 'YourServer' > 'Protocols' > 'IIOP'. Verify if IIOP is enabled. Default IIOP port is typically 7001 (same as admin) or 7002 for managed servers. Use network scanning to verify IIOP ports are accepting connections.
    Affected if IIOP protocol is enabled and the WebLogic IIOP ports are reachable from untrusted networks
  4. Assess network exposure of WebLogic ports
    Review firewall rules, security groups, or network ACLs to determine if T3 (7001, 7002, etc.) and IIOP ports are exposed to the internet or untrusted internal networks. Check for any inbound rules allowing external access to WebLogic administration or managed server ports.
    Affected if T3 or IIOP ports are exposed to network segments without proper access controls or are internet-facing

You are affected if your WebLogic Server version is exactly 12.2.1.4.0 or 14.1.1.0.0 AND T3 or IIOP protocols are enabled and accessible from untrusted network locations.

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

Restrict network access to T3 and IIOP protocols (e.g., via firewall rules or WebLogic network channel configuration) and apply the Oracle patch when available.

Fix this in Weblogic Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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