# CVE-2016-5621: Information disclosure in n/a

> Remote authenticated users can access sensitive information in Oracle FLEXCUBE Universal Banking due to an unspecified infrastructure vulnerability.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Oct 2016
- **Updated:** 10 Oct 2024
- **Also known as:** GHSA-fgrf-593g-9mfp

## What is CVE-2016-5621?

CVE-2016-5621 is a medium-severity vulnerability in Oracle Flexcube Universal Banking, published on 25 Oct 2016. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unspecified vulnerability in the Oracle FLEXCUBE Universal Banking component in Oracle Financial Services Applications 11.3.0, 11.4.0, 12.0.1 and 12.0.3, 12.1.0, and 12.2.0 allows remote authenticated users to affect confidentiality via vectors related to INFRA, a different vulnerability than CVE-2016-5603.

Weakness: CWE-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2016-5621?

It affects 1 product.


Products: Oracle Flexcube Universal Banking.

## How do I fix CVE-2016-5621?

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

## Is CVE-2016-5621 being exploited?

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

## Other vulnerabilities in Oracle Flexcube Universal Banking

- [CVE-2018-2648](https://insights.sbomify.com/CVE-2018-2648/): Auth bypass in FLEXCUBE Universal Banking (high 8.8)
- [CVE-2016-5607](https://insights.sbomify.com/CVE-2016-5607/): Missing authorization in n/a (high 8.8)
- [CVE-2019-2754](https://insights.sbomify.com/CVE-2019-2754/): Missing authorization in FLEXCUBE Universal Banking (high 8.1)
- [CVE-2018-3015](https://insights.sbomify.com/CVE-2018-3015/): Missing authorization in FLEXCUBE Universal Banking (high 8.1)
- [CVE-2018-2649](https://insights.sbomify.com/CVE-2018-2649/): Business logic in FLEXCUBE Universal Banking (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-5621 and fix it if it is affected.

What it is: CVE-2016-5621 is a medium-severity vulnerability in Oracle Flexcube Universal Banking, published on 25 Oct 2016. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-5621 in the wild and no public exploit code.

Affected product: Oracle Flexcube Universal Banking. 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-2016-5621/ (Markdown: https://insights.sbomify.com/CVE-2016-5621/index.md)
```

## Sources

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

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