dbcve.org
Weblogic ServerApplication · Oracle

CVE-2022-21347

MEDIUM · 6.5 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 →
74/100
Remediation priority · Elevated
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: Core). 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 T3 to compromise Oracle WebLogic Server. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle WebLogic Server accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle WebLogic Server. CVSS 3.1 Base Score 6.5 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L).

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 contains a vulnerability in the Core component where an unauthenticated attacker with network access via the T3 protocol can exploit the server to achieve unauthorized update, insert, or delete access to some accessible data, plus cause a partial denial of service. The T3 protocol is used for intra-server and server-to-server communication in WebLogic environments.

MitigationApply the Oracle Critical Patch Update (CPU) that addresses CVE-2022-21347, which updates the affected WebLogic Server versions to patched releases. Additionally, restrict T3/IIOP network access to only trusted sources or disable these protocols if not required.

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
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

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

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 installation and version
    Locate the WebLogic installation directory and check for version files such as version.txt, registry.xml, or the PRODUCT_HOME/version.txt file. Common paths include /Oracle/Middleware/wlserver or C:\Oracle\Middleware\wlserver. Read the version from these files.
    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
  2. Confirm T3 protocol is enabled
    Examine the WebLogic config.xml file (typically found in the domain config directory, e.g., DOMAIN_HOME/config/config.xml). Look for Network Access Point or Server MBean definitions that explicitly enable the T3 protocol. Alternatively, check the WebLogic Administration Console under the Server > Protocols section.
    Affected if T3 protocol is explicitly enabled or the server is configured to accept T3 connections in the config.xml
  3. Verify T3 network accessibility
    Check which network interfaces and ports the WebLogic server is bound to. Review the Listen Address setting in the server configuration. Determine if the server Listen Address is bound to 0.0.0.0, a non-internal IP, or is externally accessible. Also scan for open ports commonly used by T3 (default 7001 for admin server, but varies by configuration).
    Affected if The T3 port is listening on a publicly accessible IP address or an untrusted network interface (not restricted to localhost/127.0.0.1)
  4. Check for T3 protocol filters
    Inspect the WebLogic security configuration for any T3-specific network filters or access controls. Look for WeblogicPlugin.xml or similar configuration files that may define protocol-level restrictions.
    Affected if No T3-specific network filters are configured, or the T3 protocol is allowed from any source

The environment is affected if WebLogic Server version is exactly 12.1.3.0.0, 12.2.1.3.0, 12.2.1.4.0, or 14.1.1.0.0 AND the T3 protocol is enabled and accessible from an untrusted network.

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 the Oracle Critical Patch Update (CPU) that addresses CVE-2022-21347, which updates the affected WebLogic Server versions to patched releases. Additionally, restrict T3/IIOP network access to only trusted sources or disable these protocols if not required.

Recommended fix High confidence

Apply Oracle January 2022 Critical Patch Update patches for WebLogic Server (for 12.1.3.x, ensure active Oracle support contract; for 12.2.1.4.x upgrade to 12.2.1.4 with latest patches; for 14.1.1.0.x apply latest patch set)

  1. 1. Review Oracle's January 2022 Critical Patch Update (CPU) advisory for CVE-2022-21347.
  2. 2. Navigate to Oracle Support (support.oracle.com) and search for patch updates for your specific WebLogic Server version (12.1.3.0.0, 12.2.1.3.0, 12.2.1.4.0, or 14.1.1.0.0).
  3. 3. Download and apply the applicable patch from the January 2022 CPU for your exact version.
  4. 4. After applying the patch, restart all WebLogic Server instances to ensure the fix takes effect.
  5. 5. As a compensating control, if patching is not immediately possible, restrict network access to the T3 protocol at the network/firewall level to prevent unauthenticated remote exploitation.
Caveat Patch application may require downtime for WebLogic Server restarts; test patches in non-production environment first

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
  • 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-2022-21347 — 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-21347 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