Flexcube Universal BankingApplication · Oracle

CVE-2020-14887

MEDIUM · 6.5 CVSS v3.1 Published 2020-10-21
Fix available
A fix is available. Upgrade to after 14.4.0 or later.
See remediation →
71/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.0 and 14.0.0-14.4.0. Easily exploitable 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. CVSS 3.1 Base Score 6.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/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 · high confidence

Vulnerability in Oracle FLEXCUBE Universal Banking Infrastructure component allows a low-privileged attacker with network access via HTTP to access critical data. The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) indicates confidentiality impact is High with no integrity or availability impact.

MitigationApply Oracle Critical Patch Updates for affected versions (12.3.0, 14.0.0-14.4.0). Implement network access controls to restrict web interface exposure and ensure least-privilege access controls are enforced.

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

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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify Oracle Flexcube Universal Banking installation
    Locate the Flexcube installation directory or check system inventory for Oracle Flexcube Universal Banking software. Look for application logs, configuration files, or deployment artifacts that confirm this product is installed.
    Affected if The software is present on the system
  2. Determine installed version
    Check the version of Oracle Flexcube Universal Banking by examining version files, About dialogs, or using the product's administrative interface. Common locations include installation directories, configuration files, or the web application's login page footer.
    Affected if The installed version is 12.3.0 OR falls between 14.0.0 and 14.4.0 (inclusive)
  3. Verify web interface accessibility
    Determine if the Flexcube web interface is network-accessible by testing HTTP/HTTPS connectivity to the application's URLs. Check firewall rules, reverse proxy configurations, and network segmentation settings.
    Affected if The web interface is reachable from untrusted networks (AV:N in CVSS vector)
  4. Assess account privileges
    Review user accounts configured in the Flexcube system. Determine whether low-privileged accounts exist that have network access to the application.
    Affected if Low-privileged user accounts with HTTP access to the application are present

You are affected if Oracle Flexcube Universal Banking versions 12.3.0 or 14.0.0-14.4.0 are installed and the web interface is network-accessible to low-privileged users.

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

Apply Oracle Critical Patch Updates for affected versions (12.3.0, 14.0.0-14.4.0). Implement network access controls to restrict web interface exposure and ensure least-privilege access controls are enforced.

Fix this in Flexcube Universal Banking Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-14887 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-14887 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