dbcve.org
Flexcube Universal BankingApplication · Oracle

CVE-2022-21576

MEDIUM · 6.4 CVSS v3.1 Published 2022-07-19
Fix available
A fix is available. Upgrade to after 14.3.0 or later.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 FLEXCUBE Universal Banking product of Oracle Financial Services Applications (component: Infrastructure). Supported versions that are affected are 12.3, 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 of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle FLEXCUBE Universal Banking accessible data as well as unauthorized update, insert or delete access to some of Oracle FLEXCUBE Universal Banking accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle FLEXCUBE Universal Banking. CVSS 3.1 Base Score 6.4 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/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 · moderate confidence

Vulnerability in Oracle FLEXCUBE Universal Banking's Infrastructure component allows a low-privileged attacker with network access via HTTP to potentially gain unauthorized access to critical data, modify or delete data, and cause partial denial of service. The 'difficult to exploit' classification and 'low privilege' requirement suggest the flaw may involve improper authorization checks or authentication bypass in infrastructure-level code.

MitigationApply Oracle's published security patches for the affected versions (12.3, 12.4, 14.0-14.3, 14.5). If patches are unavailable, restrict network access to the HTTP interfaces and enforce least-privilege access controls while monitoring for anomalous activity.

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
Flexcube Universal BankingApplication
Affected:>= 14.0.0, <= 14.3.0= 12.3.0= 12.4.0= 14.5.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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Oracle FLEXCUBE Universal Banking is deployed
    Review installed software inventory or application listings for Oracle Flexcube Universal Banking components. Check for associated services or application pools running on application servers.
    Affected if Oracle FLEXCUBE Universal Banking software is present in the environment
  2. Determine the installed version of Oracle FLEXCUBE Universal Banking
    Access the product's version information through its administration console, installation logs, or version query interface provided by Oracle. Compare the installed version against the affected ranges: 12.3.0, 12.4.0, 14.0.0 through 14.3.0, and 14.5.0.
    Affected if The installed version matches any of the affected versions listed
  3. Verify if the Infrastructure component is in use
    Check the deployment configuration to confirm whether the Infrastructure module or component of Oracle FLEXCUBE Universal Banking is enabled and actively processing requests.
    Affected if The Infrastructure component is deployed and operational
  4. Assess network exposure of HTTP interfaces
    Review network firewall rules, load balancer configurations, or web server settings to determine if the Oracle FLEXCUBE HTTP interfaces are accessible from untrusted networks or the internet.
    Affected if HTTP interfaces are exposed to network access beyond trusted boundaries
  5. Check for authentication and authorization configuration
    Review the security configuration files or settings related to authentication and session management within the Oracle FLEXCUBE Infrastructure component, focusing on privilege enforcement for low-privileged users.
    Affected if Authorization checks can be bypassed or are improperly enforced for low-privileged network access

The environment is affected if Oracle FLEXCUBE Universal Banking version 12.3.0, 12.4.0, 14.0.0-14.3.0, or 14.5.0 is installed with the Infrastructure component exposed to network HTTP access.

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.

From vendor data
Upgrade available Upgrade to a release after 14.3.0
Interim mitigation

Apply Oracle's published security patches for the affected versions (12.3, 12.4, 14.0-14.3, 14.5). If patches are unavailable, restrict network access to the HTTP interfaces and enforce least-privilege access controls while monitoring for anomalous activity.

Fix this in Flexcube Universal Banking Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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