dbcve.org
Weblogic ServerApplication · Oracle

CVE-2020-2828

HIGH · 7.5 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 →
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: WLS Web Services). The supported version that is affected is 10.3.6.0.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via IIOP, T3 to compromise Oracle WebLogic Server. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle WebLogic Server accessible data. CVSS 3.0 Base Score 7.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 remote vulnerability in Oracle WebLogic Server's WLS Web Services component (version 10.3.6.0.0) allows attackers with network access via IIOP or T3 protocols to gain unauthorized access to critical data or all accessible data on the WebLogic Server.

MitigationApply Oracle Critical Patch Update (CPU) that addresses CVE-2020-2828. If immediate patching is not feasible, restrict network access to IIOP and T3 ports from untrusted sources at the network perimeter.

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

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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/Middleware or Oracle/WebLogic in the filesystem). Look for the 'wlserver' directory and confirm the product name.
    Affected if WebLogic Server is not installed, this CVE does not apply.
  2. Verify the exact version number
    Check the WebLogic version by examining version.txt in the installation directory, the registry.xml file, or by running the WebLogic Scripting Tool (WLST) with the command 'print productVersion'. Compare the installed version to 10.3.6.0.0.
    Affected if The installed version is exactly 10.3.6.0.0. If the version differs (higher or lower), the environment is not affected by this specific CVE.
  3. Confirm IIOP protocol is enabled
    Check the WebLogic Server config.xml file for '<iiop>' or '<iiop-detail>' elements under the <server> configuration. Alternatively, access the WebLogic Admin Console, navigate to the server's Configuration > General tab, and verify if IIOP is enabled.
    Affected if IIOP protocol is enabled and listening on the network. If IIOP is disabled, this specific attack vector does not apply.
  4. Confirm T3 protocol is enabled
    Check the WebLogic Server config.xml file for '<t3>' elements. Alternatively, in the WebLogic Admin Console, verify the Enable T3 checkbox under the server's Configuration > General settings. T3 typically listens on the same port as the admin server (default 7001).
    Affected if T3 protocol is enabled and accessible over the network. If T3 is disabled, this specific attack vector does not apply.

The environment is affected only if Oracle WebLogic Server version 10.3.6.0.0 is installed AND either IIOP or T3 protocol is 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 Oracle Critical Patch Update (CPU) that addresses CVE-2020-2828. If immediate patching is not feasible, restrict network access to IIOP and T3 ports from untrusted sources at the network perimeter.

Fix this in Weblogic Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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