Weblogic ServerApplication · Oracle

CVE-2022-21292

HIGH · 7.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 →
84/100
Remediation priority · High
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: Samples). Supported versions that are affected are 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 unauthorized access to critical data or complete access to all Oracle WebLogic Server accessible data. CVSS 3.1 Base Score 7.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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

Oracle WebLogic Server contains an unauthenticated information disclosure vulnerability in its Samples component. An attacker with network access via HTTP can exploit this to gain unauthorized access to critical or all accessible data on the server. The CVSS vector indicates no authentication required and high confidentiality impact with low attack complexity.

MitigationDisable or remove the Samples component from production Oracle WebLogic Server deployments. Apply Oracle's official patch when available. If Samples are required, restrict network access to trusted networks only.

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.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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 WebLogic Server version
    Check the installed Oracle WebLogic Server version using the Oracle Inventory or by inspecting the weblogic.Server class version (typically found in $ORACLE_HOME/wlserver/server/lib/weblogic.jar or via the WebLogic Administration Console under 'Servers' > 'Monitoring' > 'General'). Compare against affected versions 12.2.1.4.0 and 14.1.1.1.0.
    Affected if The installed version exactly matches 12.2.1.4.0 or 14.1.1.0.0 (these are the only affected versions listed).
  2. Determine if Samples component is deployed
    Check if the WebLogic Samples application is deployed. This is typically located under $ORACLE_HOME/wlserver/samples/server/examples/build or accessed via the WebLogic Administration Console under 'Deployments' > 'Samples'. Inspect the deployment configuration files and check for an active Samples application ear/war.
    Affected if The Samples application is deployed and in an 'Active' or 'Running' state in WebLogic.
  3. Verify Samples endpoint accessibility
    Attempt to access the Samples component endpoints via HTTP. Common paths include /examples/ or /sample-app/ under the server's HTTP port. Check if the HTTP listener on the WebLogic port (default 7001) responds to requests targeting sample-related URL paths without requiring authentication.
    Affected if The HTTP port is externally accessible and the Samples endpoint responds without authentication.
  4. Check network exposure of WebLogic HTTP port
    Review firewall rules, network ACLs, and WebLogic network channel configurations to determine if the HTTP port (typically 7001) is bound to a publicly accessible network interface or is reachable from untrusted networks.
    Affected if The WebLogic HTTP port is reachable from untrusted network segments or exposed to the internet.

You are affected only if you run WebLogic Server version 12.2.1.4.0 or 14.1.1.0.0, the Samples component is deployed and active, and the HTTP port hosting Samples is network-accessible to untrusted users.

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

Disable or remove the Samples component from production Oracle WebLogic Server deployments. Apply Oracle's official patch when available. If Samples are required, restrict network access to trusted networks only.

Recommended fix Moderate confidence

Oracle WebLogic Server 12.2.1.4.0 and 14.1.1.0.0 should be upgraded to the latest available patched versions as specified in Oracle's CPU advisory containing CVE-2022-21292

  1. 1. Check Oracle's Critical Patch Update (CPU) advisory for January 2022 or subsequent CPUs for CVE-2022-21292 patch availability
  2. 2. Download the applicable security patch from Oracle Support (My Oracle Support) using the patch ID referenced in the CPU advisory
  3. 3. Review Oracle's workaround documentation - consider disabling or removing the 'Samples' component if not in use
  4. 4. Apply the patch in a test environment first following Oracle's standard patching procedures
  5. 5. Verify the patch was applied successfully and the vulnerability is remediated
  6. 6. Deploy the patched version to production
Caveat Review Oracle's patch documentation for any known issues or restart requirements; test thoroughly in non-production before applying to production

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

Fix this in Weblogic Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-21292 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