dbcve.org
Weblogic ServerApplication · Oracle

CVE-2024-21274

HIGH · 7.5 CVSS v3.1 Published 2024-10-15
Fix available
A fix is available. Upgrade to after 14.1.1.0.0 or later.
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: Console). 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

Denial of Service vulnerability in Oracle WebLogic Server Console component affecting versions 12.2.1.4.0 and 14.1.1.0.0. Unauthenticated remote attackers can exploit this via HTTP to cause the server to hang or crash repeatedly, resulting in complete availability loss.

MitigationApply Oracle Critical Patch Update addressing CVE-2024-21274, or upgrade to a patched version of WebLogic Server. As a temporary control, restrict network access to the WebLogic Console to trusted IPs only.

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
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 installed WebLogic Server version
    Check the WebLogic installation directory for version files, or query the WebLogic Administration Console 'About WebLogic' page, or inspect the inventory file at $ORACLE_HOME/inventory/ContentsXML/comps.xml
    Affected if The installed version falls within the range 12.2.1.4.0 to 14.1.1.0.0 (inclusive)
  2. Verify WebLogic Admin Console is enabled
    Confirm the WebLogic Administration Console application is deployed and running. Check via WebLogic Administration Console 'Deployments' page or by listing deployed applications via WLST
    Affected if The Admin Console application is deployed and in an active state
  3. Check Console HTTP port exposure
    Identify the port the WebLogic Admin Console is listening on (typically 7001 or configured port). Use 'netstat -an | grep <console-port>' or check the AdminServer listen address in config.xml
    Affected if The Console port is reachable over network (not bound to localhost only, or not behind a firewall)

Your environment is affected if WebLogic Server version is 12.2.1.4.0 through 14.1.1.0.0 AND the Admin Console is accessible over HTTP from the network.

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
Upgrade available Upgrade to a release after 14.1.1.0.0
Interim mitigation

Apply Oracle Critical Patch Update addressing CVE-2024-21274, or upgrade to a patched version of WebLogic Server. As a temporary control, restrict network access to the WebLogic Console to trusted IPs only.

Recommended fix Moderate confidence

Apply January 2025 CPU patch or upgrade to latest 12.2.1.4.x / 14.1.1.x version per Oracle's CPU release notes

  1. 1. Review the Oracle Critical Patch Update (CPU) advisory for January 2025 to obtain the specific patch identifier for CVE-2024-21274
  2. 2. Navigate to Oracle Support and download the applicable patch for your WebLogic Server version
  3. 3. Apply the patch following Oracle's standard patching procedure: backup the current Oracle Middleware home, stop all WebLogic Server processes, apply the patch using OPatch, and restart the servers
  4. 4. Verify the patch was applied successfully by checking the WebLogic Server version and confirming the CVE is no longer detectable
Caveat Standard Oracle CPU patching typically has minimal risk; ensure to test in non-production environment first as with any patch

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

Fix this in Weblogic Server 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 the upgrade done

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-21274 — 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-21274 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