# CVE-2016-8320: Missing authorization in FLEXCUBE Enterprise Limits and Collateral Management

> Unauthenticated attackers can modify and read data in Oracle FLEXCUBE via HTTP, requiring user interaction to exploit.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Jan 2017
- **Updated:** 9 Oct 2024
- **Also known as:** GHSA-c257-pr57-9cr7

## What is CVE-2016-8320?

CVE-2016-8320 is a medium-severity missing authorization vulnerability in Oracle FLEXCUBE Enterprise Limits and Collateral Management, published on 27 Jan 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Vulnerability in the Oracle FLEXCUBE Enterprise Limits and Collateral Management component of Oracle Financial Services Applications (subcomponent: Core). Supported versions that are affected are 12.0.0 and 12.0.2. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle FLEXCUBE Enterprise Limits and Collateral Management. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle FLEXCUBE Enterprise Limits and Collateral Management, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle FLEXCUBE Enterprise Limits and Collateral Management accessible data as well as unauthorized read access to a subset of Oracle FLEXCUBE Enterprise Limits and Collateral Management accessible data. CVSS v3.0 Base Score 6.1 (Confidentiality and Integrity impacts).

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Oracle Flexcube Enterprise Limits and Collateral Management.

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

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

## Is CVE-2016-8320 being exploited?

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

## Other vulnerabilities in Oracle FLEXCUBE Enterprise Limits and Collateral Management

- [CVE-2017-3493](https://insights.sbomify.com/CVE-2017-3493/): Information disclosure in FLEXCUBE Enterprise Limits and Collateral Management (high 8.5)
- [CVE-2018-3051](https://insights.sbomify.com/CVE-2018-3051/): Missing authorization in FLEXCUBE Enterprise Limits and Collateral Management (high 8.1)
- [CVE-2018-3041](https://insights.sbomify.com/CVE-2018-3041/): Denial of service in FLEXCUBE Enterprise Limits and Collateral Management (medium 6.5)
- [CVE-2017-3491](https://insights.sbomify.com/CVE-2017-3491/): Information disclosure in FLEXCUBE Enterprise Limits and Collateral Management (medium 6.5)
- [CVE-2018-3037](https://insights.sbomify.com/CVE-2018-3037/): Missing authorization in FLEXCUBE Enterprise Limits and Collateral Management (medium 6.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-8320 is a medium-severity missing authorization vulnerability in Oracle FLEXCUBE Enterprise Limits and Collateral Management, published on 27 Jan 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-8320 in the wild and no public exploit code.

Affected product: Oracle FLEXCUBE Enterprise Limits and Collateral Management. 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-8320/ (Markdown: https://insights.sbomify.com/CVE-2016-8320/index.md)
```

## Sources

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

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