# CVE-2022-21581: Missing authorization in Banking Trade Finance

> Low-privileged attackers can modify, read, or disrupt Oracle Banking Trade Finance data via HTTP with user interaction.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Jul 2022
- **Updated:** 24 Sep 2024
- **Also known as:** GHSA-56r8-63jp-jmf7

## What is CVE-2022-21581?

CVE-2022-21581 is a medium-severity missing authorization vulnerability in Oracle Corporation Banking Trade Finance, published on 19 Jul 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

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

## Which versions are affected by CVE-2022-21581?

It affects 1 product.


Products: Oracle Banking Trade Finance.

## How do I fix CVE-2022-21581?

No fix has been published for CVE-2022-21581 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-21581 being exploited?

There is no known exploitation of CVE-2022-21581 in the wild and no public exploit code.

## Other vulnerabilities in Oracle Corporation Banking Trade Finance

- [CVE-2026-61102](https://insights.sbomify.com/CVE-2026-61102/): Missing authorization in Oracle Banking Trade Finance (high 8.1)
- [CVE-2026-61105](https://insights.sbomify.com/CVE-2026-61105/): Missing authorization in Oracle Banking Trade Finance (high 8.1)
- [CVE-2022-21582](https://insights.sbomify.com/CVE-2022-21582/): Missing authorization in Banking Trade Finance (medium 6.7)
- [CVE-2022-21585](https://insights.sbomify.com/CVE-2022-21585/): Missing authorization in Banking Trade Finance (medium 6.7)
- [CVE-2022-21583](https://insights.sbomify.com/CVE-2022-21583/): Information disclosure in Banking Trade Finance (medium 6.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-21581 and fix it if it is affected.

What it is: CVE-2022-21581 is a medium-severity missing authorization vulnerability in Oracle Corporation Banking Trade Finance, published on 19 Jul 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-21581 in the wild and no public exploit code.

Affected product: Oracle Corporation Banking Trade Finance. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-21581/ (Markdown: https://insights.sbomify.com/CVE-2022-21581/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-21581
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-21581
- OSV: https://osv.dev/vulnerability/CVE-2022-21581

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-21581/
Summaries are generated and may contain mistakes; the official description above is the record.