CVE-2022-21577
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 FLEXCUBE Universal Banking product of Oracle Financial Services Applications (component: Infrastructure). Supported versions that are affected are 12.1-12.4, 14.0-14.3 and 14.5. Difficult to exploit vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle FLEXCUBE Universal Banking. 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 FLEXCUBE Universal Banking accessible data as well as unauthorized access to critical data or complete access to all Oracle FLEXCUBE Universal Banking accessible data. CVSS 3.1 Base Score 6.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/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 confidenceVulnerability in Oracle FLEXCUBE Universal Banking Infrastructure component allows low privileged attackers with network access via HTTP to modify or access critical data. Successful exploitation requires human interaction (UI:R), indicating a social engineering or click-based attack vector.
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.1.0, <= 12.4.0>= 14.0.0, <= 14.3.0= 14.5.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
- High
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/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 Oracle FLEXCUBE Universal Banking installation versionLocate the Oracle FLEXCUBE installation directory and check for version information in VERSION.txt, manifest files, or query the Oracle Inventory (oratab or oraInventory) for the Flexcube component version.Affected if Installed version matches >= 12.1.0 AND <= 12.4.0, OR >= 14.0.0 AND <= 14.3.0, OR = 14.5.0
-
Confirm web application is network-accessibleVerify the Oracle FLEXCUBE Universal Banking web interface (HTTP/HTTPS endpoints) is exposed to the network and accessible to low privileged users.Affected if The FLEXCUBE web interface is reachable from the network by users with low privileges
-
Check if end-user browser access is enabledDetermine whether direct browser-based access to the FLEXCUBE application is enabled for end users, as this is required for the human interaction (UI:R) attack vector.Affected if End users have direct interactive access to the web interface
The environment is affected if Oracle FLEXCUBE Universal Banking version is 12.1.0-12.4.0, 14.0.0-14.3.0, or exactly 14.5.0, and the web application is accessible to low privileged users who can be socially engineered.
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 · scopedApply Oracle Critical Patch Update for FLEXCUBE Universal Banking. Restrict network access to the application and implement additional user awareness training since human interaction is required for exploitation.
Upgrade to version 14.6.0 or later (or the latest supported version within your major release train)
- Check the Oracle Critical Patch Update for July 2022 (or the nearest subsequent CPU) on oracle.com for CVE-2022-21577
- Download and apply the relevant Oracle FLEXCUBE Universal Banking patch for your version from Oracle Support
- After patching, verify the Infrastructure component has been updated by checking the version or consulting Oracle documentation
- Test the patch in a non-production environment before deploying to production
- Coordinate the patch deployment with the appropriate change management process as the fix requires human interaction to complete
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21577 — 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-21577 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