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 3 May 2022.
Weblogic ServerApplication · Oracle

CVE-2020-14883

HIGH · 7.2 CVSS v3.1 Published 2020-10-21
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 High EPSS Public exploit Remotely reachable 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 10.3.6.0.0, 12.1.3.0.0, 12.2.1.3.0, 12.2.1.4.0 and 14.1.1.0.0. Easily exploitable vulnerability allows high privileged attacker with network access via HTTP to compromise Oracle WebLogic Server. Successful attacks of this vulnerability can result in takeover of Oracle WebLogic Server. CVSS 3.1 Base Score 7.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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

Vulnerability in Oracle WebLogic Server Console allows high privileged attackers with network access via HTTP to compromise the server, resulting in full takeover with high impact to confidentiality, integrity, and availability. The vulnerability affects versions 10.3.6.0.0 through 14.1.1.0.0 and is described as easily exploitable.

MitigationApply Oracle Critical Patch Update (CPU) patches for CVE-2020-14883 to affected WebLogic Server installations. Restrict console access to trusted networks and privileged users as a compensating control until patching is completed.

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:= 10.3.6.0.0= 12.1.3.0.0= 12.2.1.3.0= 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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/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. Identify WebLogic Server installation and version
    Locate the WebLogic installation directory (typically under $ORACLE_HOME or /opt/oracle). Check for version information in the registry or product version files such as <weblogic_home>/registry.xml or the installation inventory. Alternatively, examine the console WAR file version if deployed.
    Affected if The installed version matches any of: 10.3.6.0.0, 12.1.3.0.0, 12.2.1.3.0, 12.2.1.4.0, or 14.1.1.0.0
  2. Identify running WebLogic processes
    On the server, use commands like 'ps -ef | grep java' or 'jps' to identify Java processes running WebLogic. Look for process arguments containing '-Dweblogic.Name=' or referencing the WebLogic home directory.
    Affected if A WebLogic Server process is running with an affected version from step 1
  3. Verify if WebLogic Console is accessible
    Check if the console is bound to network interfaces by reviewing the ListenAddress configuration in the domain config.xml (typically in <domain>/config/config.xml). Also check firewall rules and network exposure for typical console ports (7001, 7002, 7003, 9002).
    Affected if The console ListenAddress is set to 0.0.0.0 or a public IP, or the console port is exposed beyond localhost

If WebLogic Server is running with version 10.3.6.0.0, 12.1.3.0.0, 12.2.1.3.0, 12.2.1.4.0, or 14.1.1.0.0 and the console is network-accessible, the environment is affected by CVE-2020-14883.

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) patches for CVE-2020-14883 to affected WebLogic Server installations. Restrict console access to trusted networks and privileged users as a compensating control until patching is completed.

Recommended fix Moderate confidence

Oracle WebLogic Server 14.1.1.0.0 or later (or apply October 2020 CPU to existing 10.3.6/12.1.3/12.2.1.x installations)

  1. 1. Review Oracle Critical Patch Update Advisory for October 2020 (or later) which addresses CVE-2020-14883
  2. 2. Identify your current Oracle WebLogic Server exact version number
  3. 3. Download and apply the October 2020 Critical Patch Update (or subsequent CPU containing the fix) from Oracle Support
  4. 4. Alternatively, upgrade to a version beyond the affected releases: 12.2.1.4.0 to a newer supported version like 14.1.1.0.0 or later
  5. 5. After applying patch or upgrade, restart Oracle WebLogic Server services
  6. 6. Verify the patch was applied successfully by checking the Oracle WebLogic Server version and testing console access
Caveat Oracle CPUs may introduce compatibility issues with custom applications; regression testing recommended after patch application

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

Fix this in Weblogic Server Exploited in the wild — priority engagement
  • 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-2020-14883 — 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-2020-14883 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