# CVE-2018-3021: Information disclosure in Banking Payments

> Unauthenticated attackers can read sensitive data from Oracle Banking Payments via HTTP, requiring immediate patching by financial institutions.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jul 2018
- **Updated:** 2 Oct 2024
- **Also known as:** GHSA-36p7-fgf7-w6rh

## What is CVE-2018-3021?

CVE-2018-3021 is a medium-severity vulnerability in Oracle Corporation Banking Payments, published on 18 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in the Oracle Banking Payments component of Oracle Financial Services Applications (subcomponent: Payments Core). Supported versions that are affected are 12.2.0, 12.3.0, 12.4.0, 12.5.0 and 14.1.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Banking Payments. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Oracle Banking Payments accessible data. CVSS 3.0 Base Score 5.3 (Confidentiality impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N).

## Which versions are affected by CVE-2018-3021?

It affects 1 product.


Products: Oracle Banking Payments.

## How do I fix CVE-2018-3021?

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

## Is CVE-2018-3021 being exploited?

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

## Other vulnerabilities in Oracle Corporation Banking Payments

- [CVE-2018-2705](https://insights.sbomify.com/CVE-2018-2705/): Auth bypass in Banking Payments (high 8.8)
- [CVE-2018-3027](https://insights.sbomify.com/CVE-2018-3027/): Missing authorization in Banking Payments (high 8.1)
- [CVE-2018-2704](https://insights.sbomify.com/CVE-2018-2704/): Missing authorization in Banking Payments (high 8.1)
- [CVE-2020-2713](https://insights.sbomify.com/CVE-2020-2713/): Missing authorization in Banking Payments (high 7.1)
- [CVE-2020-14896](https://insights.sbomify.com/CVE-2020-14896/): Information disclosure in Banking Payments (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-3021 and fix it if it is affected.

What it is: CVE-2018-3021 is a medium-severity vulnerability in Oracle Corporation Banking Payments, published on 18 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-3021 in the wild and no public exploit code.

Affected product: Oracle Corporation Banking Payments. 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-2018-3021/ (Markdown: https://insights.sbomify.com/CVE-2018-3021/index.md)
```

## Sources

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

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