dbcve.org
Flexcube Universal BankingApplication · Oracle

CVE-2021-2323

MEDIUM · 5.9 CVSS v3.1 Published 2021-07-21
Fix available
A fix is available. Upgrade to after 14.4.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges 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: Flex-Branch). Supported versions that are affected are 12.3, 12.4, 14.0-14.4 and . Difficult to exploit vulnerability allows unauthenticated 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. CVSS 3.1 Base Score 5.9 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/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 confidence

Unauthenticated HTTP-based vulnerability in the Flex-Branch component of Oracle FLEXCUBE Universal Banking allows remote attackers to access critical confidential data. The high complexity and difficult exploitation requirements suggest specific conditions must be met, though the exact vulnerability type (injection, broken authentication, etc.) is not specified in the advisory.

MitigationRestrict network access to Flex-Branch interfaces, apply Oracle security patches when available, and ensure web-facing endpoints follow defense-in-depth principles. Since no authentication is required, network segmentation is critical.

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.4.0= 12.3.0= 12.4.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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

  1. Confirm Oracle FLEXCUBE Universal Banking installation
    Check for FLEXCUBE installation directories (commonly under $ORACLE_HOME/flexcube or C:\Oracle\flexcube), running Windows services, or Java processes listening on typical banking application ports (typically 8080, 8443, or custom ports)
    Affected if Oracle FLEXCUBE Universal Banking software is present in the environment
  2. Identify installed FLEXCUBE version
    Locate version information in the installation directory - check for version.txt, about files, or examine the Oracle database tables if you have DBA access. The version typically appears in installation logs or can be retrieved via the FLEXCUBE Administrator console
    Affected if Installed version matches 12.3.0, 12.4.0, or falls within 14.0.0 through 14.4.0 inclusive
  3. Verify Flex-Branch component is deployed
    Inspect the application deployment structure for the Flex-Branch module. Check web.xml or application configuration files for flexbranch servlets, or look for flexbranch-related WAR files or directories in the application server
    Affected if Flex-Branch web component is deployed and accessible within the application
  4. Determine HTTP interface network exposure
    Review network configuration, firewall rules, and load balancer settings to determine if Flex-Branch HTTP/HTTPS endpoints (typically on ports 8080/8443 or configured application ports) are reachable from untrusted networks or the internet
    Affected if Flex-Branch HTTP interfaces are accessible from network segments outside the trusted internal network

You are affected if Oracle FLEXCUBE Universal Banking is installed with a version in the 12.3.0, 12.4.0, or 14.0.0-14.4.0 range, the Flex-Branch component is deployed, and its HTTP interfaces are network-accessible without authentication requirements.

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.4.0
Interim mitigation

Restrict network access to Flex-Branch interfaces, apply Oracle security patches when available, and ensure web-facing endpoints follow defense-in-depth principles. Since no authentication is required, network segmentation is critical.

Fix this in Flexcube Universal Banking Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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