dbcve.org
Weblogic ServerApplication · Oracle

CVE-2022-21616

MEDIUM · 5.2 CVSS v3.1 Published 2022-10-18
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
54/100
Remediation priority · Moderate
Zero-click Patch available

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: Web Container). Supported versions that are affected are 12.2.1.3.0, 12.2.1.4.0 and 14.1.1.0.0. Difficult to exploit vulnerability allows high privileged attacker with logon to the infrastructure where Oracle WebLogic Server executes to compromise Oracle WebLogic Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle WebLogic Server as well as unauthorized update, insert or delete access to some of Oracle WebLogic Server accessible data and unauthorized read access to a subset of Oracle WebLogic Server accessible data. CVSS 3.1 Base Score 5.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/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

A detailed technical summary for this CVE is being prepared.

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:= 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
Local
Complexity
High
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
High

CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:H

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
Patch available Apply the vendor patch
Vendor patch www.oracle.com →
Recommended fix High confidence

Apply Oracle Critical Patch Update October 2022 (CPUOCT2022) - specifically the patches for WebLogic Server 12.2.1.3.x, 12.2.1.4.x, or 14.1.1.x respectively. Oracle issues Patch Set Updates (PSUs) that continue the same version line (e.g., 12.2.1.3.x, 12.2.1.4.x, 14.1.1.x).

  1. 1. Review the Oracle Critical Patch Update advisory for October 2022 at https://www.oracle.com/security-alerts/cpuoct2022.html to obtain the specific patch identifiers for WebLogic Server.
  2. 2. Identify the correct patch for your specific WebLogic Server version (12.2.1.3.0, 12.2.1.4.0, or 14.1.1.0.0).
  3. 3. Download the required patch from Oracle Support using the patch IDs listed in the October 2022 CPU.
  4. 4. Apply the patch following Oracle's standard patching procedure: backup the Oracle Middleware home, stop all WebLogic Server processes, apply the patch using OPatch, then restart the servers.
  5. 5. Verify the patch was applied successfully by checking the WebLogic Server version and confirming the CVE is no longer listed as exploitable.
Caveat Oracle patch updates are generally backward compatible within the same version line; however, always test in a non-production environment before applying to production.

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

We can apply and verify the patch for your build — typical engagement from $1,600. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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