# CVE-2017-3483: Information disclosure in FLEXCUBE Enterprise Limits and Collateral Management

> A high-privileged attacker with local access can exploit this vulnerability to gain unauthorized access to critical data in Oracle FLEXCUBE.

- **Severity:** Medium 4.4 (`CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Apr 2017
- **Updated:** 7 Oct 2024
- **Also known as:** GHSA-vw62-3g5x-pwj8

## What is CVE-2017-3483?

CVE-2017-3483 is a medium-severity vulnerability in Oracle Corporation FLEXCUBE Enterprise Limits and Collateral Management, published on 24 Apr 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Vulnerability in the Oracle FLEXCUBE Enterprise Limits and Collateral Management component of Oracle Financial Services Applications (subcomponent: Limits and Collateral). Supported versions that are affected are 12.0.0 and 12.1.0. Easily "exploitable" vulnerability allows high privileged attacker with logon to the infrastructure where Oracle FLEXCUBE Enterprise Limits and Collateral Management executes to compromise Oracle FLEXCUBE Enterprise Limits and Collateral Management. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle FLEXCUBE Enterprise Limits and Collateral Management accessible data. CVSS 3.0 Base Score 4.4 (Confidentiality impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N).

## Which versions are affected by CVE-2017-3483?

It affects 1 product.


Products: Oracle Flexcube Enterprise Limits and Collateral Management.

## How do I fix CVE-2017-3483?

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

## Is CVE-2017-3483 being exploited?

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

## Other vulnerabilities in Oracle Corporation 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-2017-3483 and fix it if it is affected.

What it is: CVE-2017-3483 is a medium-severity vulnerability in Oracle Corporation FLEXCUBE Enterprise Limits and Collateral Management, published on 24 Apr 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-3483 in the wild and no public exploit code.

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

## Sources

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

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