CVE-2020-14750
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: 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 unauthenticated 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 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 confidenceA critical unauthenticated remote code execution vulnerability in Oracle WebLogic Server's Console component allows remote attackers to completely compromise the server via HTTP requests without any authentication or user interaction, achieving full confidentiality, integrity, and availability impact.
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= 10.3.6.0.0= 12.1.3.0.0= 12.2.1.3.0= 12.2.1.4.0= 14.1.1.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 versionLocate the WebLogic installation and determine the exact version number. Check for version files in the installation directory, the Oracle inventory file, or query the server using WLST (WebLogic Scripting Tool) with 'getMajorVersion()' and 'getMinorVersion()' commands. The console about page also displays the version if accessible.Affected if The installed version is 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
-
Confirm WebLogic Console is deployedVerify that the WebLogic Console application is deployed and running in your domain. Check the deployed-applications configuration in your domain's config.xml, or query the WebLogic Administration interface, or use WLST to list deployed applications and look for 'console' in the name.Affected if The Console application (console.war/console.ear) is deployed and active
-
Check Console network exposureIdentify the port the WebLogic Console is listening on (default 7001 for admin console). Review network firewall rules, load balancer settings, and the ListenAddress configuration in config.xml to determine if this port is accessible from network segments outside the trusted admin network.Affected if The Console port is reachable from untrusted or external network locations via HTTP
You are affected if your WebLogic Server version matches exactly 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, the Console is deployed, and the Console HTTP port is network-accessible without proper segmentation.
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.
dbcve · scopedApply Oracle's quarterly security patches for CVE-2020-14750 (or upgrade to a patched version) and restrict network access to WebLogic Console/admin interfaces via firewall or authentication mechanisms.
Apply Oracle October 2020 Critical Patch Update (CPU) to affected versions, or upgrade to WebLogic Server 14.1.1.0.0 with latest CPU applied
- Download and apply Oracle Critical Patch Update (CPU) October 2020 which addresses CVE-2020-14750 from Oracle's official patch repository
- For Oracle WebLogic Server 10.3.6.0.0: Apply patch following Oracle's README instructions for WLS 10.3.6
- For Oracle WebLogic Server 12.1.3.0.0: Apply patch following Oracle's README instructions for WLS 12.1.3
- For Oracle WebLogic Server 12.2.1.3.0: Apply patch following Oracle's README instructions for WLS 12.2.1.3
- For Oracle WebLogic Server 12.2.1.4.0: Apply patch following Oracle's README instructions for WLS 12.2.1.4
- For Oracle WebLogic Server 14.1.1.0.0: Apply patch following Oracle's README instructions for WLS 14.1.1
- After applying the patch, restart all WebLogic Server instances to ensure the fix takes effect
- Verify the patch was applied successfully by checking the WebLogic Server version and testing the Console functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14750 — 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-2020-14750 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