CVE-2024-21183
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 · uneditedVulnerability 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 confidenceUnauthenticated remote vulnerability in Oracle WebLogic Server Core component (versions 12.2.1.4.0 and 14.1.1.0.0) exploitable via T3/IIOP network protocols. Attackers with network access can gain unauthorized read access to critical or all accessible data without any credentials.
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= 12.2.1.4.0= 14.1.1.0.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify WebLogic Server installation and versionLocate the WebLogic installation directory (typically $ORACLE_HOME/wlserver) and check the version file (often in utils/bsu or the installation manifest). Common locations: $ORACLE_HOME/wlserver/modules or check the registry/config.xml for the version attribute.Affected if The installed version is exactly 12.2.1.4.0 or exactly 14.1.1.0.0 (these are the only affected versions per the CVE)
-
Determine if T3 protocol listener is activeReview the WebLogic Server configuration (config.xml) for Network Access Points or listen ports configured for T3 protocol. Alternatively, inspect active network listeners using 'netstat -an | grep' for common T3 ports (typically 7001 for admin, but custom ports may be configured).Affected if T3 protocol listener is enabled and exposed on a network-accessible port (T3 must be active for this vulnerability to be exploitable)
-
Determine if IIOP protocol listener is activeReview the WebLogic Server configuration (config.xml) for IIOP-enabled server instances. Check for IIOP listener ports (typically 2809 or custom configured). Use 'netstat -an | grep' to identify listening IIOP ports.Affected if IIOP protocol listener is enabled and exposed on a network-accessible port (IIOP must be active for this vulnerability to be exploitable)
-
Verify network accessibility of T3/IIOP portsFrom an external host (or using network tools), test connectivity to the identified T3 and IIOP ports (e.g., using telnet, nc, or nmap). Check firewall rules and network segmentation that may or may not restrict access.Affected if T3 or IIOP ports are reachable from untrusted networks (the vulnerability is exploitable by attackers with network access to these protocols)
A system is affected if it runs WebLogic Server version 12.2.1.4.0 or 14.1.1.0.0 AND has T3 or IIOP protocols enabled and network-accessible to untrusted actors.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply Oracle Critical Patch Update (CPU) containing the fix for this vulnerability. If patches unavailable, restrict network access to T3/IIOP ports via firewall rules or network segmentation, and disable these protocols if not required by the application.
Upgrade to the latest Oracle WebLogic Server 14.1.1.x release or apply the latest CPU patch for 12.2.1.4.0
- Identify the current Oracle WebLogic Server version in use (12.2.1.4.0 or 14.1.1.0.0)
- Review Oracle's official Critical Patch Update (CPU) advisories for the quarter that addresses CVE-2024-21183
- Obtain and apply the latest Oracle WebLogic Server patch that addresses this vulnerability from Oracle Support (support.oracle.com)
- Alternatively, upgrade to the most recent supported version of Oracle WebLogic Server (14.1.1.x series receives latest security patches)
- After applying the patch or upgrade, restart the WebLogic Server components
- Verify the patch was applied successfully by checking the WebLogic Server version and reviewing applied patches
- Restrict network access to T3 and IIOP protocols using WebLogic Server network filters or firewall rules if immediate patching is not feasible
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21183 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-21183 in production — separate from our analysis above.
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.
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.
- 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