dbcve.org
Weblogic ServerApplication · Oracle

CVE-2024-20927

HIGH · 8.6 CVSS v3.1 Published 2024-02-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/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. While the vulnerability is in Oracle WebLogic Server, attacks may significantly impact additional products (scope change). 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 8.6 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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

Unauthenticated HTTP-based vulnerability in Oracle WebLogic Server Core component (versions 12.2.1.4.0 and 14.1.1.0.0) allows remote attackers to modify critical data through easily exploitable network attacks. The flaw leverages the HTTP interface with no authentication required, resulting in high integrity impact.

MitigationApply Oracle Critical Patch Update (CPU) for CVE-2024-20927 to affected WebLogic Server versions. As interim compensating controls, restrict HTTP/HTTPS access to trusted networks only and consider deploying a WAF to filter malicious requests.

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
Changed
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/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 WebLogic Server installation
    Locate WebLogic installation directories (commonly under $ORACLE_HOME/wlserver or C:\Oracle\Middleware\wlserver) or check for running WebLogic processes (java processes with weblogic.Server)
    Affected if WebLogic Server is found on the system
  2. Determine installed WebLogic version
    Check the version file in the installation directory (e.g., wlserver_14.1.1.0/registry.xml or the product.version file), or access the WebLogic Administration Console via HTTP/HTTPS and view the 'About' page
    Affected if Installed version matches exactly 12.2.1.4.0 or 14.1.1.0.0
  3. Verify HTTP interface is enabled
    Check WebLogic configuration files (config.xml) for Network Access Points listening on typical HTTP ports (7001, 7002) or run 'java -jar wlserver.jar -version' to confirm the server can expose HTTP listeners
    Affected if HTTP listener is enabled on any accessible port (default 7001 for admin console)
  4. Assess network exposure of HTTP ports
    Use netstat or equivalent to identify which network interfaces the WebLogic HTTP ports are bound to (0.0.0.0 indicates all interfaces), and check if firewall rules allow external access
    Affected if HTTP ports are accessible from untrusted network interfaces or the internet

A user is affected if they run exactly version 12.2.1.4.0 or 14.1.1.0.0 of Oracle WebLogic Server with its HTTP interface 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.

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

Apply Oracle Critical Patch Update (CPU) for CVE-2024-20927 to affected WebLogic Server versions. As interim compensating controls, restrict HTTP/HTTPS access to trusted networks only and consider deploying a WAF to filter malicious requests.

Recommended fix Moderate confidence

Upgrade to the latest WebLogic Server 12.2.1.x or 14.1.1.x version with the January 2024 CPU applied

  1. 1. Review the Oracle Critical Patch Update (CPU) advisory for January 2024 to obtain the specific patch for CVE-2024-20927
  2. 2. Identify the appropriate patch for your WebLogic Server version (12.2.1.4.0 or 14.1.1.0.0) from the Oracle support documentation
  3. 3. Download the patch from Oracle Support (support.oracle.com) using your Oracle Support credentials
  4. 4. Apply the patch following Oracle's standard patch application procedures for WebLogic Server
  5. 5. Restart the WebLogic Server instances to ensure the patch takes effect
  6. 6. Verify the patch was applied successfully by checking the WebLogic Server version and confirming the vulnerability is resolved
Caveat Review Oracle's patch prerequisites and known issues for the January 2024 CPU before applying

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

Fix this in Weblogic Server Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing12.0 h
  • Review / QA4.0 h
34.0 hours of engineering $5,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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