dbcve.org
Fusion MiddlewareApplication · Oracle

CVE-2024-21215

HIGH · 7.5 CVSS v3.1 Published 2024-10-15
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 HTTP to compromise Oracle WebLogic Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle WebLogic Server. CVSS 3.1 Base Score 7.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).

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

CVE-2024-21215 is a denial-of-service vulnerability in the Oracle WebLogic Server Core component. Unauthenticated attackers can exploit this flaw via HTTP requests to cause the server to hang or repeatedly crash, resulting in complete availability loss.

MitigationApply Oracle Critical Patch Update (CPU) containing the fix for this vulnerability to affected versions 12.2.1.4.0 and 14.1.1.0.0, or implement network-level filtering to restrict HTTP access to trusted sources until patching is feasible.

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
Fusion MiddlewareApplication
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
None
Integrity
None
Availability
High

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

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 Oracle WebLogic Server installation
    Check for WebLogic processes running (ps aux | grep -i weblogic) or look for WebLogic installation directories such as $ORACLE_HOME or /u01/oracle/.../wlserver
    Affected if WebLogic Server process is running or installation directory exists on the system
  2. Determine installed WebLogic version
    Check the WebLogic version by examining the installation manifest or version file within the wlserver directory, or access the Administration Console and navigate to 'Server' > 'Configuration' to view the version information
    Affected if Installed version matches 12.2.1.4.0 or 14.1.1.0.0 exactly
  3. Verify HTTP listener exposure
    Review the WebLogic Server configuration (config.xml) for network listeners, and check if the HTTP or HTTPS ports (typically 7001, 7002, or custom ports) are bound to network interfaces accessible from untrusted networks
    Affected if HTTP listeners are bound to externally accessible IP addresses without network filtering
  4. Check for denial-of-service indicators
    Examine WebLogic server logs (located in the logs directory under the domain configuration) for patterns indicating hangs, crashes, or repeated restarts, and monitor for sudden server unresponsiveness on HTTP endpoints
    Affected if Server logs show repeated hangs, crashes, or inability to handle HTTP requests since the vulnerability disclosure date

A user is affected if they have Oracle WebLogic Server version 12.2.1.4.0 or 14.1.1.0.0 running with HTTP access exposed to untrusted networks, and they observe server hangs or crashes without alternative explanation.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Update (CPU) containing the fix for this vulnerability to affected versions 12.2.1.4.0 and 14.1.1.0.0, or implement network-level filtering to restrict HTTP access to trusted sources until patching is feasible.

Recommended fix Moderate confidence

For long-term stability, upgrade to the latest Oracle WebLogic Server 14.1.1.x release when feasible

  1. Navigate to My Oracle Support (support.oracle.com) and search for CVE-2024-21215 or the October 2024 Critical Patch Update (CPU)
  2. Locate the Oracle WebLogic Server security patch for this CVE
  3. Download and apply the relevant patch for your version (12.2.1.4.0 or 14.1.1.0.0) following Oracle's standard patch application process
  4. Apply the patch to all affected WebLogic Server instances
  5. Restart the WebLogic Server components as required by the patch documentation
  6. Verify the patch was applied successfully by checking the WebLogic Server version and confirming the vulnerability is resolved
Caveat Standard Oracle CPU patching has minimal risk but always test in non-production first; upgrading to newer major versions may require compatibility testing

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fusion Middleware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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