dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 3 May 2022.
Weblogic ServerApplication · Oracle

CVE-2020-14882

CRITICAL · 9.8 CVSS v3.1 Published 2020-10-21
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
In the wild High EPSS Public exploit 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: 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 confidence

Oracle WebLogic Server Console component contains an authentication bypass vulnerability (CVE-2020-14882) that allows unauthenticated remote attackers to execute arbitrary code via specially crafted HTTP requests. Combined with CVE-2020-14883 (which allows bypassing authentication to access the admin console), this enables complete server compromise without credentials.

MitigationApply Oracle Critical Patch Update (October 2020 or later) to remediate this vulnerability. If immediate patching is not possible, restrict network access to the WebLogic Console port (typically 7001) to trusted IPs only via firewall or WAF.

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 version
    Check the version file in the Oracle middleware home directory, typically under <MW_HOME>/wlserver_10.3 or check the startup logs for the version string like 'WebLogic Server Version: 10.3.6.0.0'
    Affected if The installed version matches any of these: 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
  2. Verify WebLogic Console is network accessible
    Scan for open ports 7001 (Admin Server) or 7002 (SSL) on network interfaces, or check the config.xml file in the domain directory for the ListenAddress and ListenPort settings
    Affected if The console port (7001/7002) is bound to a routable network address rather than localhost only
  3. Confirm console is reachable without authentication
    Attempt to access http://<host>:7001/console or http://<host>:7001/console/login.jsp and verify the login page loads without being redirected to an authentication error
    Affected if The console login page loads successfully from a non-trusted network, indicating the authentication bypass can be tested
  4. Check for recent exploitation indicators
    Review WebLogic access logs (typically in <DOMAIN_HOME>/servers/<SERVER_NAME>/logs/access.log) for unusual requests containing '../' path traversal patterns or multiple /console/consolejndi.portal entries
    Affected if Requests with path traversal sequences (../) targeting the console endpoint appear in the logs

If WebLogic Server 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 AND the console port is exposed to untrusted networks, the environment is vulnerable to CVE-2020-14882.

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 Update (October 2020 or later) to remediate this vulnerability. If immediate patching is not possible, restrict network access to the WebLogic Console port (typically 7001) to trusted IPs only via firewall or WAF.

Recommended fix High confidence

Upgrade to WebLogic Server 12.2.1.5.0 or later, or 14.1.1.2.0 or later

  1. Apply Oracle Critical Patch Update October 2020 (CPU) which includes the fix for CVE-2020-14882
  2. Alternatively, upgrade to WebLogic Server 12.2.1.5.0 or later
  3. Alternatively, upgrade to WebLogic Server 14.1.1.2.0 or later
  4. After applying the patch or upgrade, restart the WebLogic Server services
  5. Verify the console is accessible and the vulnerability is mitigated by attempting the exploitation path
Caveat Major version upgrades may require testing of existing applications for compatibility; review Oracle upgrade documentation before proceeding

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

Fix this in Weblogic Server Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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