dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 4 Jun 2026.
Weblogic ServerApplication · Oracle

CVE-2024-21182

HIGH · 7.5 CVSS v3.1 Published 2024-07-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
In the wild 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 a deserialization vulnerability in its Core component, exploitable via T3 and IIOP protocols. Unauthenticated remote attackers can achieve unauthorized access to critical data by sending specially crafted serialized Java objects through these protocols, which are enabled by default in affected versions 12.2.1.4.0 and 14.1.1.0.0.

MitigationApply Oracle Critical Patch Update to address this vulnerability; as an interim measure, restrict or disable network access to T3/IIOP ports and implement network segmentation to limit exposure.

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 if Oracle WebLogic Server is installed
    Look for WebLogic processes (java processes with -Dweblogic.Name or related flags) or check installation directories such as $ORACLE_HOME/wlserver or C:\Oracle\Middleware\wlserver
    Affected if No WebLogic Server installation found means not affected by this specific product vulnerability
  2. Determine the installed WebLogic Server version
    Check the version file in the WebLogic installation directory, typically under wlserver/server/lib or look for the file 'registry.xml' or '.product.properties' that contains the version string, or access the Admin Console 'About WebLogic' page
    Affected if The installed version equals 12.2.1.4.0 or 14.1.1.0.0 exactly matches the vulnerable versions
  3. Check if T3 protocol is enabled and accessible
    T3 typically listens on the administration port (default 7001) or a configured managed server port. Verify by reviewing the WebLogic Server configuration in config.xml under the <server> <listen-port> elements, or check network listening ports using 'netstat -an | grep 7001' or 'ss -tlnp | grep 7001'
    Affected if T3 protocol listener is active and bound to a network-accessible IP addresses the system is potentially vulnerable
  4. Check if IIOP protocol is enabled and accessible
    IIOP typically uses ports 7002 (default) for managed servers. Review the WebLogic config.xml for <iiop> or <iiop-message> enabled settings, or check listening ports using 'netstat -an | grep 7002' or 'ss -tlnp | grep 7002'
    Affected if IIOP protocol listener is enabled and exposed on network-accessible interfaces the system is potentially vulnerable

Your environment is affected if you have WebLogic Server version 12.2.1.4.0 or 14.1.1.0.0 with T3 or IIOP protocols enabled and exposed to network 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Update to address this vulnerability; as an interim measure, restrict or disable network access to T3/IIOP ports and implement network segmentation to limit exposure.

Fix this in Weblogic Server Exploited in the wild — priority engagement
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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