Banking PaymentsApplication · Oracle

CVE-2020-14896

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 Banking Payments product of Oracle Financial Services Applications (component: Core). Supported versions that are affected are 14.1.0-14.4.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Banking Payments. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Banking Payments 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 · moderate confidence

Vulnerability in Oracle Banking Payments Core component allows low-privileged authenticated attackers via HTTP to access critical data. The CVSS vector (C:H/I:N/A:N) indicates primary confidentiality impact with no integrity or availability effects. The 'easily exploitable' designation suggests straightforward attack execution.

MitigationApply Oracle Critical Patch Update for affected versions 14.1.0-14.4.0. If patches unavailable, restrict network access to banking payment interfaces and review user privilege assignments.

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
Banking PaymentsApplication
Affected:>= 14.1.0, <= 14.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
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 Banking Payments installation
    Query the application inventory or deployment records for Oracle Banking Payments. Check application metadata files, deployment descriptors, or use the Oracle system inventory tools if available.
    Affected if Oracle Banking Payments is present in the environment
  2. Determine installed version
    Locate the version file or check the About/Version information within the Oracle Banking Payments application console, or query the application's database metadata tables for the version string.
    Affected if The installed version falls within the range >= 14.1.0 and <= 14.4.0
  3. Verify HTTP interface exposure
    Review network configuration, load balancer rules, or web server configuration to confirm the banking payment HTTP endpoints are accessible over the network from untrusted zones.
    Affected if HTTP interfaces for Oracle Banking Payments are externally accessible or accessible from less-trusted network segments
  4. Confirm authentication is enabled
    Review the authentication configuration settings in the Oracle Banking Payments admin console or security configuration files to verify that user authentication is enforced on the payment interfaces.
    Affected if The application accepts authenticated HTTP sessions for low-privileged users

The environment is affected if Oracle Banking Payments version 14.1.0 through 14.4.0 is installed with its HTTP interface accessible to authenticated 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 Update for affected versions 14.1.0-14.4.0. If patches unavailable, restrict network access to banking payment interfaces and review user privilege assignments.

Fix this in Banking Payments Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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