dbcve.org
Weblogic ServerApplication · Oracle

CVE-2022-21386

MEDIUM · 6.1 CVSS v3.1 Published 2022-01-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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.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 require human interaction from a person other than the attacker and while the vulnerability is in Oracle WebLogic Server, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle WebLogic Server accessible data as well as unauthorized read access to a subset of Oracle WebLogic Server accessible data. CVSS 3.1 Base Score 6.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N).

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

Vulnerability in Oracle WebLogic Server's Web Container component allows unauthenticated attackers with network access via HTTP to compromise the server. Requires human interaction (UI:R) and results in unauthorized read and limited write/delete access to a subset of accessible data. The scope change (S:C) indicates attacks may impact additional products beyond WebLogic Server itself.

MitigationApply Oracle Critical Patch Update (January 2022) for WebLogic Server. As an interim control, restrict network access to WebLogic Server admin interfaces and implement WAF rules to detect and block malicious HTTP requests.

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:= 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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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 Oracle WebLogic Server installation
    Locate the WebLogic installation directory (typically $ORACLE_HOME/wlserver or $MW_HOME/wlserver). Check for the existence of the WebLogic Server installation and confirm the product name.
    Affected if WebLogic Server is installed on the system
  2. Determine installed WebLogic Server version
    Check the version file in the WebLogic installation: look for the file or output from the versionInfo script (typically in wlserver/server/lib or use java -jar wlserver.jar -ignoreSysPrereqs). The version should be listed as 12.1.3.0.0, 12.2.1.3.0, 12.2.1.4.0, or 14.1.1.0.0
    Affected if The installed version matches exactly 12.1.3.0.0, 12.2.1.3.0, 12.2.1.4.0, or 14.1.1.0.0
  3. Verify Web Container component is deployed
    Check if the WebLogic Web Container (embedded HTTP server) is enabled by reviewing the configuration in the WebLogic Administration Console under Servers > [server name] > Protocols > HTTP, or check the config.xml file for <http> elements under the server configuration.
    Affected if The Web Container HTTP protocol is enabled and listening on a network interface
  4. Confirm network accessibility of WebLogic HTTP ports
    Identify the HTTP listen port (default 7001 for admin server, or configured port for managed servers) by reviewing the config.xml or using WebLogic Administration Console. Verify if this port is accessible from untrusted networks (check firewall rules, iptables, or network ACLs).
    Affected if HTTP ports are exposed to untrusted network access without proper network segmentation

A system is affected if Oracle WebLogic Server versions 12.1.3.0.0, 12.2.1.3.0, 12.2.1.4.0, or 14.1.1.0.0 are installed with the Web Container accessible via HTTP from untrusted networks.

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 (January 2022) for WebLogic Server. As an interim control, restrict network access to WebLogic Server admin interfaces and implement WAF rules to detect and block malicious HTTP requests.

Recommended fix High confidence

Oracle provides patches via Critical Patch Updates rather than version upgrades; apply the January 2022 CPU patch for WebLogic Server 12.1.3, 12.2.1.3, 12.2.1.4, or 14.1.1.0.0

  1. Apply the Oracle Critical Patch Update (CPU) that addresses CVE-2022-21386. For Oracle WebLogic Server, this vulnerability was addressed in the January 2022 Critical Patch Update.
  2. Download and install the appropriate patch from Oracle Support (support.oracle.com) using Oracle OPatch or the Oracle WebLogic Server patch installation process.
  3. Restart all Oracle WebLogic Server instances after applying the patch to ensure the fix takes effect.
  4. Verify the patch was applied successfully by checking the Oracle WebLogic Server version and confirming the security fix is active.
  5. If immediate patching is not possible, restrict network access to the WebLogic Server HTTP ports to trusted sources only, and disable or limit parsing of untrusted XML input in the Web Container if configuration options exist.
Caveat Patches are generally backward-compatible but test in a non-production environment first; review Oracle patch readme for any pre-installation requirements or known issues

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

Fix this in Weblogic Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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