CVE-2022-21473
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 Banking Treasury Management product of Oracle Financial Services Applications (component: Infrastructure). The supported version that is affected is 14.5. Difficult to exploit vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Banking Treasury Management. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Banking Treasury Management accessible data as well as unauthorized read access to a subset of Oracle Banking Treasury Management accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Banking Treasury Management. CVSS 3.1 Base Score 5.9 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:H/A:L).
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 confidenceVulnerability in Oracle Banking Treasury Management Infrastructure component (version 14.5) allows a low-privileged attacker with network access via HTTP to compromise the system. Successful exploitation requires human interaction and enables unauthorized creation, deletion, or modification of critical data, along with read access to a subset of data and partial denial of service.
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= 14.5CVSS 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
- High
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:H/A:L
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 Oracle Banking Treasury Management versionCheck the installed version of Oracle Banking Treasury Management through the Oracle opatch lsinventory command, Oracle Enterprise Manager, or by querying the Oracle inventory tables (like VERSION_COMMENTS in DBA_REGISTRY). Compare the installed version to the affected version 14.5.Affected if The installed version is exactly 14.5.0.0.0 or reports as version 14.5.
-
Verify Oracle Banking Treasury Management Infrastructure componentConfirm the Oracle Banking Treasury Management Infrastructure component is installed. Check the DBA_REGISTRY or Oracle inventory to confirm this specific subcomponent exists in the environment.Affected if The Oracle Banking Treasury Management Infrastructure component is present and reporting version 14.5.
-
Assess network exposure of the Banking Treasury systemReview network configuration to determine if the Oracle Banking Treasury Management web interfaces (typically accessed via HTTP/HTTPS) are exposed to network access beyond the internal trusted network.Affected if The system is accessible via network (HTTP) from locations outside the trusted internal network.
-
Review user privilege assignmentsAudit the Oracle user accounts and roles in the Banking Treasury Management system to identify any low-privileged accounts that exist, as exploitation targets a low-privileged attacker.Affected if Low-privileged user accounts exist in the Oracle Banking Treasury Management system.
-
Evaluate human interaction requirementsAssess whether typical user workflows in the Treasury Management system involve actions where an attacker could socially engineer a user into performing a malicious action (such as clicking a malicious link).Affected if Users can be tricked into performing actions through the web interface that could be leveraged by an attacker.
A user is affected if their Oracle Banking Treasury Management Infrastructure component is exactly version 14.5 and is exposed to network access, as the vulnerability requires both the specific version and network accessibility for a low-privileged attacker to exploit with human interaction.
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 the Oracle Critical Patch Update that addresses CVE-2022-21473. Since the vulnerability requires human interaction and has high attack complexity, prioritize patching based on exposure and ensure staff are trained to recognize social engineering attempts.
- Consultation4.0 h
- Implementation12.0 h
- Testing16.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21473 — 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-21473 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