dbcve.org
Weblogic ServerApplication · Oracle

CVE-2020-2798

HIGH · 7.2 CVSS v3.1 Published 2020-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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: WLS Web Services). Supported versions that are affected are 10.3.6.0.0, 12.1.3.0.0, 12.2.1.3.0 and 12.2.1.4.0. Easily exploitable vulnerability allows high privileged attacker with network access via IIOP, T3 to compromise Oracle WebLogic Server. Successful attacks of this vulnerability can result in takeover of Oracle WebLogic Server. CVSS 3.0 Base Score 7.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/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's WLS Web Services component allows a high-privileged attacker with network access via IIOP or T3 protocols to achieve remote code execution and complete takeover of the WebLogic Server. The flaw is easily exploitable with low complexity and no user interaction required.

MitigationApply the relevant Oracle Critical Patch Update to the affected WebLogic Server versions (10.3.6.0.0, 12.1.3.0.0, 12.2.1.3.0, 12.2.1.4.0). If immediate patching is not feasible, restrict network access to IIOP/T3 ports or disable these protocols if not required by the application.

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

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
    Check the WebLogic installation directory for the version file, typically in the BEA_HOME or ORACLE_HOME directory, or run: java -jar wlserver_*.jar -print java -verbose | grep -i version. Common locations: $ORACLE_HOME/wlserver_10.3 or $ORACLE_HOME/wlserver_12.1 or $ORACLE_HOME/wlserver_12.2
    Affected if The installed version matches exactly 10.3.6.0.0, 12.1.3.0.0, 12.2.1.3.0, or 12.2.1.4.0
  2. Verify WLS Web Services module is in use
    Check the WebLogic configuration files (config.xml) for <wls:webservices> or <webservices> elements, or inspect the deployed applications for WAR/JAR files containing WebServices annotations and the wls-web-services.jar library
    Affected if WebLogic Server has WLS Web Services deployed or configured
  3. Confirm IIOP protocol is enabled
    Check the WebLogic Server Administration Console under Servers > [ServerName] > Protocols > IIOP, or inspect config.xml for <iiop-enabled>true</iiop-enabled> under the server's configuration
    Affected if IIOP protocol is enabled on any managed server or admin server
  4. Confirm T3 protocol is enabled
    Check the WebLogic Server Administration Console under Servers > [ServerName] > Protocols > T3, or inspect config.xml for <t3-enabled>true</t3-enabled> under the server's configuration
    Affected if T3 protocol is enabled on any managed server or admin server
  5. Identify exposed IIOP/T3 network listeners
    Review the server's network configuration to determine which network addresses and ports the IIOP (default 7001/7002) and T3 (default 7001) listeners are bound to, using 'netstat -anp' or reviewing the config.xml <network-access-point> entries
    Affected if IIOP or T3 ports are bound to externally accessible network interfaces (non-loopback)

A user is affected if they run any of the four specific WebLogic versions (10.3.6.0.0, 12.1.3.0.0, 12.2.1.3.0, or 12.2.1.4.0) with the WLS Web Services component AND have either IIOP or T3 protocols enabled and network-accessible.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant Oracle Critical Patch Update to the affected WebLogic Server versions (10.3.6.0.0, 12.1.3.0.0, 12.2.1.3.0, 12.2.1.4.0). If immediate patching is not feasible, restrict network access to IIOP/T3 ports or disable these protocols if not required by the application.

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