dbcve.org
Weblogic ServerApplication · Oracle

CVE-2022-21259

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 · moderate confidence

Insecure direct object reference or similar access control flaw in the Samples component of Oracle WebLogic Server versions 12.2.1.4.0 and 14.1.1.0.0 allows unauthenticated attackers via HTTP to achieve unauthorized read, insert, update, and delete access to a subset of accessible data. The attack requires human interaction (social engineering victim to click a malicious link) and may impact additional products beyond WebLogic Server due to scope change.

MitigationApply Oracle Critical Patch Update (CPU) patches for January 2022 or later that address CVE-2022-21259. If immediate patching is not feasible, restrict network access to WebLogic Server Sample applications and monitor for suspicious HTTP requests targeting sample endpoints.

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 installation version
    Locate the WebLogic Server installation and check the version. Common ways include: checking the installation directory for version files, using the WebLogic Administration Console, or running version inquiry commands if available in your deployment. Compare the installed version against the affected versions 12.2.1.4.0 and 14.1.1.0.0.
    Affected if The installed version is exactly 12.2.1.4.0 or 14.1.1.0.0
  2. Determine if Samples component is deployed
    Check the WebLogic Server deployment configuration to see if the Samples application is currently deployed and running. This can be done through the WebLogic Administration Console under Deployments, or by reviewing the deployment configuration files and domain configuration.
    Affected if The Samples application is deployed and running on the affected WebLogic Server version
  3. Verify network accessibility of Sample endpoints
    Inspect network configuration and firewall rules to determine if the WebLogic Server HTTP ports are accessible from untrusted networks. Also review the HTTP server configuration to confirm sample application endpoints are exposed.
    Affected if WebLogic Server HTTP ports and sample application endpoints are accessible from untrusted or external networks without proper access restrictions
  4. Review HTTP access logs for suspicious Sample endpoint requests
    Examine WebLogic Server HTTP access logs for unusual or unauthorized requests targeting sample application endpoints. Look for patterns indicating enumeration or exploitation attempts against sample functionality.
    Affected if Logs show unauthorized or anomalous HTTP requests to sample application endpoints from untrusted sources

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

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 (CPU) patches for January 2022 or later that address CVE-2022-21259. If immediate patching is not feasible, restrict network access to WebLogic Server Sample applications and monitor for suspicious HTTP requests targeting sample endpoints.

Recommended fix Moderate confidence

Upgrade to WebLogic Server 12.2.1.4.0 with January 2022 CPU applied, or upgrade to WebLogic Server 14.1.1.0.0 or later with corresponding security patches. For long-term support, consider WebLogic Server 12.2.1.5.0 (or latest 12.2.1.x) or 14.1.1.0.0+ with all security updates.

  1. 1. Identify the current Oracle WebLogic Server version in use (12.2.1.4.0 or 14.1.1.0.0)
  2. 2. Subscribe to Oracle Critical Patch Updates (CPUs) for Oracle Fusion Middleware
  3. 3. Obtain the January 2022 Critical Patch Update (CPU) or later from Oracle Support
  4. 4. Apply the patch for CVE-2022-21259, which is addressed in the January 2022 CPU
  5. 5. Alternatively, upgrade to a later version of WebLogic Server that includes the fix
  6. 6. After applying the patch or upgrade, restart the WebLogic Server instances
  7. 7. Verify the Samples component is no longer vulnerable by testing the affected endpoints
Caveat Patches from Oracle CPUs are generally backward compatible; however, review the January 2022 CPU patch notes for any known issues specific to the Samples component

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
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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