CVE-2022-21252
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 · uneditedVulnerability 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 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.5 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 confidenceOracle WebLogic Server contains a vulnerability in its Samples component (versions 12.2.1.4.0 and 14.1.1.0.0) that allows unauthenticated attackers via HTTP to perform unauthorized read, insert, update, or delete operations on a subset of accessible data. The attack requires network access but needs no authentication or user interaction.
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= 12.2.1.4.0= 14.1.1.0.0CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Identify WebLogic Server installationLocate the WebLogic Server installation directory. Common paths include $ORACLE_HOME/wlserver or C:\Oracle\Middleware\wlserver. Check for the presence of the WebLogic installation and its version file or use the WebLogic Administration Console.Affected if WebLogic Server is not installed - the check does not apply
-
Verify the exact WebLogic Server versionCheck the version of the installed WebLogic Server. This can typically be found in the product inventory, installation logs, or by inspecting the manifest file in the wlserver directory. The version must be exactly 12.2.1.4.0 or exactly 14.1.1.0.0 to be affected.Affected if The installed version is not 12.2.1.4.0 or 14.1.1.0.0 - the environment is not vulnerable to this specific CVE
-
Confirm the Samples application is deployedCheck if the WebLogic Server has the Samples application deployed. This can be done through the WebLogic Administration Console under Deployments, or by checking the deployment configuration files in the domain config directory for a Samples application entry.Affected if The Samples application is not deployed - the vulnerability is not present in the environment even if the version matches
-
Verify the Samples application is accessibleConfirm the Samples application is in an active or running state and accessible over the network. Check the deployment status in the console or via WLST (WebLogic Scripting Tool). Also verify the HTTP listener is enabled for the admin server or managed servers.Affected if The Samples application is not running or not network-accessible - the exploitation vector is not available
The environment is affected by CVE-2022-21252 only if WebLogic Server version is exactly 12.2.1.4.0 or 14.1.1.0.0 AND the Samples application is deployed and accessible over the network.
Generated from the published advisory. Verify against your own configuration.
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 · scopedRemove or disable the Samples application from production WebLogic Server deployments, as sample applications are not required in production environments and represent unnecessary attack surface.
Apply Oracle Critical Patch Update (CPU) January 2022 or later; or upgrade to latest WebLogic Server 12.2.1.x or 14.1.x stable release
- Check Oracle Critical Patch Updates for the January 2022 release which addresses this vulnerability
- Apply the latest Oracle Critical Patch Update (CPU) for WebLogic Server
- If running in a production environment, test the patch in a non-production environment first
- Verify the Samples component has been updated or removed as part of the patch
- After applying the patch, restart the WebLogic Server to ensure the fix takes effect
- Validate that the Samples component is no longer accessible or has been secured
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2022-21252 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-21252 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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