CVE-2021-2064
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 · uneditedVulnerability in the Oracle WebLogic Server product of Oracle Fusion Middleware (component: Core Components). The supported version that is affected is 12.1.3.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 confidenceCritical unauthenticated remote code execution vulnerability in Oracle WebLogic Server 12.1.3.0.0 Core Components. Attackers can exploit this via IIOP or T3 network protocols without any authentication, achieving complete takeover of the affected WebLogic Server instance.
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= 12.1.3.0.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify WebLogic Server installation and versionLocate the WebLogic installation directory (commonly $ORACLE_HOME/wlserver) and check the version.properties or registry.xml file in the server directory, or use the WebLogic Administration Console to view the installed version.Affected if The installed version is exactly 12.1.3.0.0
-
Confirm IIOP protocol is enabledCheck the WebLogic Server configuration files (config.xml) for IIOP settings, or log into the WebLogic Administration Console and navigate to the Server > Protocols > IIOP page to verify if IIOP is enabled.Affected if IIOP protocol is enabled on the affected server instance
-
Confirm T3 protocol is enabledCheck the WebLogic Server configuration files (config.xml) for T3 settings, or log into the WebLogic Administration Console and navigate to the Server > Protocols > T3 page to verify if T3 is enabled.Affected if T3 protocol is enabled on the affected server instance
-
Assess network exposure of IIOP and T3 portsIdentify the listening ports for IIOP (default 9002) and T3 (default 7001) using netstat or by checking the server configuration, then determine if these ports are accessible from untrusted networks.Affected if The IIOP or T3 ports are exposed to untrusted network access
A user is affected if they have Oracle WebLogic Server version 12.1.3.0.0 running with IIOP or T3 protocols enabled and accessible to potential attackers.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Oracle Critical Patch Update (CPU) patches for CVE-2021-2064, or upgrade to a patched version of Oracle WebLogic Server. If immediate patching is not possible, restrict network access to IIOP and T3 ports or disable these protocols if not required.
- Consultation8.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-2064 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-2064 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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