dbcve.org
Weblogic ServerApplication · Oracle

CVE-2021-2075

CRITICAL · 9.8 CVSS v3.1 Published 2021-01-20
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: Samples). 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 unauthenticated 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.1 Base Score 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/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

Unauthenticated remote code execution vulnerability in Oracle WebLogic Server's Samples component, exploitable via IIOP and T3 network protocols. Successful exploitation grants attackers complete takeover of the WebLogic Server instance with high confidentiality, integrity, and availability impact.

MitigationApply Oracle Critical Patch Updates immediately. If patches cannot be applied, disable IIOP and T3 protocols if not required, or restrict network access to WebLogic Server ports 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= 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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
    Locate the WebLogic installation directory, typically under ORACLE_HOME or /u01/oracle. Check for the presence of wlserver_*.jar or config.xml in the domain configuration directory.
    Affected if WebLogic Server is not found on the system.
  2. Determine the installed WebLogic version
    Check the version using the WebLogic Administration Console, or inspect the file ORACLE_HOME/wlserver_*/modules/com.oracle.weblogic.server/*.jar for version information, or run 'java -jar wlserver_*.jar -invoker' to display version.
    Affected if The installed version matches 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 exactly.
  3. Check if the Samples component is deployed
    In the WebLogic Administration Console, navigate to Deployments and look for 'sample', 'examples', or 'console-sample' applications. Alternatively, check the domain's config.xml file for <app-deployment> entries referencing 'sample' or 'examples'.
    Affected if The Samples or Examples application is listed as deployed or installed.
  4. Verify if IIOP protocol is enabled
    In the WebLogic Administration Console, go to Servers > [ServerName] > Protocols > IIOP. Check if IIOP is enabled. Alternatively, inspect the server's config.xml for <iiop-enabled>true</iiop-enabled>.
    Affected if IIOP protocol is enabled on any managed server or admin server.
  5. Verify if T3 protocol is enabled
    In the WebLogic Administration Console, go to Servers > [ServerName] > Protocols > T3. Check if T3 is enabled. Alternatively, inspect the server's config.xml for <t3-enabled>true</t3-enabled>. Also check if port 7001 (default admin) or port 7002 (default managed) are open and listening.
    Affected if T3 protocol is enabled or the default T3 ports are open and accepting connections.

The environment is affected if WebLogic Server version matches any of the affected versions AND the Samples component is deployed AND either IIOP or T3 protocol is enabled.

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 Updates immediately. If patches cannot be applied, disable IIOP and T3 protocols if not required, or restrict network access to WebLogic Server ports at the network perimeter.

Recommended fix Moderate confidence

Oracle WebLogic Server 12.2.1.4.0 with January 2021 CPU applied, or upgrade to 14.1.1.2.0 with latest CPU

  1. 1. Identify the current Oracle WebLogic Server version in use by checking the installation or registry.
  2. 2. Download Oracle Critical Patch Update (CPU) January 2021 or later from Oracle Support (support.oracle.com).
  3. 3. Apply the WebLogic Server patch for CVE-2021-2075 from the CPU. For Oracle WebLogic Server 12.2.1.3.0 and 12.2.1.4.0, apply patch 32498313 or subsequent superseding patches.
  4. 4. For Oracle WebLogic Server 10.3.6.0.0, apply patch 32498313 or subsequent superseding patches.
  5. 5. For Oracle WebLogic Server 12.1.3.0.0, apply patch 32498313 or subsequent superseding patches.
  6. 6. For Oracle WebLogic Server 14.1.1.0.0, apply patch 32498313 or subsequent superseding patches.
  7. 7. Restart all WebLogic Server instances and managed servers to apply the patch.
  8. 8. Verify the patch was applied successfully using OPatch or WebLogic Server administration console.
Caveat Review Oracle CPU release notes for any compatibility issues; ensure application compatibility before deploying in production

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

Fix this in Weblogic Server Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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