LiveActive security incident?Get immediate response
CVE Record

CVE-2022-21581: Vulnerability in the Oracle Banking Trade Finance product of Oracle Financial Services Applications (compon...

Vulnerability in the Oracle Banking Trade Finance 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 Trade Finance. 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 Trade Finance accessible data as well as unauthorized read access to a subset of Oracle Banking Trade Finance accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Banking Trade Finance. 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).

MediumCVSS 5.9Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This flaw affects Oracle Banking Trade Finance 14.5. A low-privileged user who can reach the system over HTTP may be able to alter critical data, read some data, or cause partial service disruption, but exploitation is difficult and requires another person's interaction.

Executive priority

Treat this as a moderate priority for financial systems. The exploit conditions reduce urgency, but possible critical data modification in a banking trade finance platform warrants timely validation and vendor-guided remediation.

Technical view

CVE-2022-21581 is an Oracle Banking Trade Finance Infrastructure vulnerability in supported version 14.5. The CVSS 3.1 vector is AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:H/A:L, indicating network reachability over HTTP, low privileges, high complexity, required user interaction, and highest impact to integrity.

Likely exposure

Exposure appears limited to organizations running Oracle Banking Trade Finance 14.5, especially where authenticated low-privileged users can access the HTTP interface involved in the Infrastructure component.

Exploitation context

The source bundle does not show known active exploitation or CISA KEV listing. The vulnerability is described as difficult to exploit and dependent on low privileges, network access via HTTP, and human interaction by someone other than the attacker.

Researcher notes

No CWE is provided in the source bundle. Integrity impact is the main concern, with lower confidentiality and availability impacts. Evidence does not include exploit details, proof of exploitation, or a named standalone workaround beyond Oracle CPU guidance.

Mitigation direction

  • Check Oracle's July 2022 Critical Patch Update for product-specific remediation guidance.
  • Apply applicable Oracle-supplied fixes for Oracle Banking Trade Finance 14.5 where relevant.
  • Limit HTTP access to trusted networks and authorized users where operationally possible.
  • Review low-privileged account access to the affected application workflows.

Validation and detection

  • Confirm whether Oracle Banking Trade Finance 14.5 is deployed in the environment.
  • Verify patch status against Oracle's July 2022 Critical Patch Update guidance.
  • Identify whether low-privileged users can reach the application over HTTP.
  • Review recent logs for unusual critical data changes or partial service disruption indicators.
Prepared
Confidence
medium
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-21581 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:H/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:H/A:L1.24.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.9Medium
CVSS 3.1 vector shape for CVE-2022-21581Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:H/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Oracle CorporationBanking Trade Finance14.5Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.