dbcve.org
Weblogic ServerApplication · Oracle

CVE-2024-21175

CRITICAL · 9.1 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
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 creation, deletion or modification access to critical data or all Oracle WebLogic Server accessible data. CVSS 3.1 Base Score 7.5 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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

Vulnerability in Oracle WebLogic Server's Core component allows unauthenticated remote attackers with network access via HTTP to create, delete, or modify critical data. The low attack complexity and no privilege requirement make it easily exploitable.

MitigationApply Oracle Critical Patch Update addressing this vulnerability for versions 12.2.1.4.0 and 14.1.1.0.0; implement network segmentation and restrict HTTP access as interim controls.

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Verify WebLogic Server installation exists
    Locate WebLogic installation directories (commonly /oracle/weblogic, /u01/oracle, C:\Oracle\WebLogic, or check for BEA_HOME environment variable). Look for the Middleware or wlserver directory structure.
    Affected if No WebLogic Server installation found means this CVE does not apply to your environment.
  2. Determine installed WebLogic version
    Check the version file in the Oracle home directory, typically <WL_HOME>/inventory/registry.xml, or examine the manifest file in <WL_HOME>/wlserver/lib/weblogic.jar (view META-INF/MANIFEST.MF). Alternatively, check the WebLogic console header or startup logs for the exact version number.
    Affected if Installed version exactly matches 12.2.1.4.0 or 14.1.1.0.0; partial version matches (e.g., starting with 12.2.1.4 or 14.1.1) should be verified against Oracle's official version matrix for patch status.
  3. Confirm HTTP listener is enabled and reachable
    Verify WebLogic HTTP ports are listening (default 7001 for admin server, 7002-7003 for managed servers). Use 'netstat -an | grep 7001' or Test HTTP connectivity to http://<host>:7001/console. The vulnerability requires network access via HTTP.
    Affected if HTTP ports are open and accessible from network, increasing exposure to unauthenticated attackers.
  4. Identify exposed WebLogic endpoints
    Enumerate accessible HTTP endpoints (such as /console, /ws_utc, /_async/asyncResponse, or custom web services). Check the WebLogic configuration files (config.xml) for deployed applications with HTTP-enabled channels.
    Affected if Unauthenticated HTTP-accessible endpoints exist without additional authentication barriers beyond WebLogic form-based login.

Your environment is affected by this CVE if Oracle WebLogic Server versions 12.2.1.4.0 or 14.1.1.0.0 are installed AND HTTP network access to the WebLogic ports is possible from untrusted networks.

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 addressing this vulnerability for versions 12.2.1.4.0 and 14.1.1.0.0; implement network segmentation and restrict HTTP access as interim controls.

Recommended fix Moderate confidence

Apply latest Oracle Critical Patch Update (CPU) containing fix for CVE-2024-21175, or upgrade to the most recent supported WebLogic Server 12.2.1.x or 14.1.1.x release per Oracle's official support lifecycle

  1. Check Oracle Critical Patch Update advisories for CVE-2024-21175 at https://www.oracle.com/security-alerts/
  2. Download and apply the relevant Oracle WebLogic Server patch from Oracle Support (patch number can be obtained from the CPU advisory)
  3. Restart WebLogic Server services after applying the patch
  4. Verify the patch was applied successfully by checking the WebLogic Server version and testing the affected component
Caveat Oracle quarterly patches may require regression testing; consult Oracle support documentation for any known incompatibilities

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

Fix this in Weblogic Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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