dbcve.org
Banking PaymentsApplication · Oracle

CVE-2022-21475

MEDIUM · 5.9 CVSS v3.1 Published 2022-04-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
63/100
Remediation priority · Elevated
Remotely reachable

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: Infrastructure). The supported version that is affected is 14.5. Difficult to exploit vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Banking Payments. 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 Banking Payments accessible data as well as unauthorized read access to a subset of Oracle Banking Payments accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Banking Payments. CVSS 3.1 Base Score 5.9 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:H/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 Banking Payments version 14.5 Infrastructure component. The flaw allows a low-privileged attacker with network access via HTTP to perform unauthorized data operations (create, delete, modify, read) and cause partial denial of service. The 'difficult to exploit' nature and requirement for human interaction suggests the attack requires specific conditions or chained exploits, likely involving an authorization bypass or privilege escalation weakness in the Infrastructure layer that handles authentication or data access controls.

MitigationApply Oracle Critical Patch Update (CPU) for April 2022 that addresses this vulnerability in Oracle Banking Payments version 14.5. If patching is delayed, restrict network access to the banking application from untrusted networks and enforce strict role-based access controls as a compensating control.

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.5

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
Required
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:H/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 Oracle Banking Payments installation
    Check for Oracle Banking Payments installation directories (commonly under $ORACLE_HOME or C:\Oracle\Middleware), look for 'Oracle Banking Payments' service entries in Windows Services or process listings, or check application inventory/asset records
    Affected if Oracle Banking Payments software is present on the system
  2. Determine the installed version
    Examine version files in the installation directory (typically version.txt, about.html, or the OPatch inventory), check the Oracle Enterprise Manager console for product version information, or query the database schema version if accessible
    Affected if The installed version is exactly 14.5 (this CVE affects only this specific version)
  3. Verify Infrastructure component is configured
    Check if the Infrastructure module/component is enabled in the Oracle Banking Payments configuration (look for infrastructure-related configuration files in conf/ or config/ directories, or check the application module status via admin console)
    Affected if The Infrastructure component is deployed and active as part of the Oracle Banking Payments installation
  4. Assess network accessibility of HTTP interface
    Determine if the Oracle Banking Payments HTTP port (typically 7001-7003 or custom ports) is listening on external interfaces, check network firewall rules allowing inbound access to the application ports, and verify if the application is accessible from untrusted networks
    Affected if The HTTP interface is reachable from network-accessible hosts, particularly untrusted networks

A user is affected if they have Oracle Banking Payments version 14.5 installed with the Infrastructure component enabled and the HTTP interface exposed to network access, allowing a low-privileged attacker to potentially perform unauthorized data operations.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Update (CPU) for April 2022 that addresses this vulnerability in Oracle Banking Payments version 14.5. If patching is delayed, restrict network access to the banking application from untrusted networks and enforce strict role-based access controls as a compensating control.

Fix this in Banking Payments 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 help mitigating

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-21475 — 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-21475 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