CVE-2022-21453
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: Console). Supported versions that are affected are 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 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 (scope change). 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 confidenceOracle WebLogic Server Console vulnerability allowing unauthenticated attackers via HTTP to gain unauthorized read and partial write access to server data. Requires human interaction (likely malicious link/iframe) to exploit and can impact additional products due to scope change.
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.3.0= 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify WebLogic Server installation and versionCheck the WebLogic version by reviewing the server startup logs, the Oracle Inventory file (oraInventory/ContentsXML/inventory.xml), or by logging into the Administration Console and checking the 'About WebLogic Server' page under the 'Diagnostics' menu.Affected if The installed version matches 12.2.1.3.0, 12.2.1.4.0, or 14.1.1.0.0 exactly.
-
Verify if WebLogic Administration Console is accessible over HTTPConfirm whether the console endpoint (typically at /console/) is reachable via HTTP (port 7001 by default) from untrusted networks. Check the Network Access Point configuration in the admin console or review the config.xml file for console channel settings.Affected if The console is exposed over HTTP without authentication restrictions or behind a properly configured firewall.
-
Confirm console authentication settingsReview the WebLogic Security Realm configuration under 'Security Realms' in the Administration Console, or examine the security filter and authentication provider settings in config.xml to verify that unauthenticated requests to the console endpoint are not being processed.Affected if The console accepts unauthenticated or improperly authenticated HTTP requests.
-
Check for recent console access or suspicious activityReview WebLogic HTTP access logs and the console audit log (if enabled) for unusual GET requests to console endpoints, especially those containing unexpected parameters or originating from untrusted sources. Check for any unauthorized session creation or authentication attempts.Affected if There are unexplained console access patterns or evidence of exploitation attempts.
You are affected if your WebLogic Server version is exactly 12.2.1.3.0, 12.2.1.4.0, or 14.1.1.0.0 AND the Administration Console is exposed to unauthenticated HTTP access from untrusted networks.
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.
From vendor dataApply Oracle Critical Patch Update (CPU) containing the fix for CVE-2022-21453 to affected WebLogic Server versions. If patching is not immediately possible, restrict console access to trusted networks and implement additional input validation at upstream proxies.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21453 — 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-21453 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