dbcve.org
Weblogic ServerApplication · Oracle

CVE-2022-21257

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: 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 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

Oracle WebLogic Server contains a vulnerability in its Samples component (versions 12.2.1.4.0 and 14.1.1.0.0) exploitable via HTTP without authentication. The attack requires human interaction and allows unauthorized read and limited write access to a subset of accessible data.

MitigationRemove or disable the vulnerable sample application(s) from the WebLogic Server deployment, or apply the Oracle patch when available. If samples are not needed in production, ensure they are removed entirely rather than just disabled.

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
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 WebLogic Server version
    Log into the WebLogic Administration Console and navigate to 'Environment' > 'Servers', or use WLST command 'ls('/ServerLifeCycleRuntimes')'. Alternatively, check the manifest file in the installation directory: $ORACLE_HOME/wlserver/manifest/weblogic.jar or the config.xml file for the version attribute.
    Affected if The installed version is exactly 12.2.1.4.0 or exactly 14.1.1.0.0
  2. Verify if Samples component is deployed
    In the WebLogic Administration Console, navigate to 'Deployments' and review the list of installed applications. Look for sample applications typically named 'examples', 'sample', or 'DemoPortal'. From WLST, use 'ls('/AppDeployments')' to list all deployed applications.
    Affected if Any sample application is shown as 'Installed' or 'Active' in the Deployments list
  3. Confirm samples are accessible over HTTP
    Attempt to access common sample application URLs such as 'http://hostname:port/examples' or 'http://hostname:port/sample' where port is the HTTP listen port. A successful HTTP response indicates the samples are active.
    Affected if The sample application responds with HTTP 200 or returns sample content
  4. Check for sample application files on disk
    Examine the domain directory for sample application files. Typical paths include $DOMAIN_HOME/servers/ServerName/tmp/_WL_user/ or $DOMAIN_HOME/applications/. Look for directories containing 'sample' or 'example' in the name.
    Affected if Sample application directories exist in the domain's application folders

You are affected only if your WebLogic Server version is exactly 12.2.1.4.0 or 14.1.1.0.0 AND the Samples component is deployed and accessible.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Remove or disable the vulnerable sample application(s) from the WebLogic Server deployment, or apply the Oracle patch when available. If samples are not needed in production, ensure they are removed entirely rather than just disabled.

Fix this in Weblogic Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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