# CVE-2017-3245: Information disclosure in FLEXCUBE Direct Banking

> Unauthenticated attackers can read sensitive data via HTTP if a user interacts with a malicious link, affecting Oracle FLEXCUBE Direct Banking users.

- **Severity:** Medium 4.7 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/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-hjm2-f7rv-xqwp

## What is CVE-2017-3245?

CVE-2017-3245 is a medium-severity vulnerability in Oracle FLEXCUBE Direct Banking, 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 Direct Banking component of Oracle Financial Services Applications (subcomponent: Pre-Login). Supported versions that are affected are 12.0.2 and 12.0.3. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle FLEXCUBE Direct Banking. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle FLEXCUBE Direct Banking, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Oracle FLEXCUBE Direct Banking accessible data. CVSS v3.0 Base Score 4.7 (Confidentiality impacts).

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Oracle Flexcube Direct Banking.

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

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

## Is CVE-2017-3245 being exploited?

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

## Other vulnerabilities in Oracle FLEXCUBE Direct Banking

- [CVE-2016-0699](https://insights.sbomify.com/CVE-2016-0699/): Other in n/a (critical 9.1)
- [CVE-2017-10181](https://insights.sbomify.com/CVE-2017-10181/): Denial of service in FLEXCUBE Direct Banking (medium 6.8)
- [CVE-2020-14890](https://insights.sbomify.com/CVE-2020-14890/): Information disclosure in FLEXCUBE Direct Banking (medium 6.5)
- [CVE-2020-14897](https://insights.sbomify.com/CVE-2020-14897/): Information disclosure in FLEXCUBE Direct Banking (medium 6.5)
- [CVE-2019-2980](https://insights.sbomify.com/CVE-2019-2980/): Information disclosure in FLEXCUBE Direct Banking (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-3245 and fix it if it is affected.

What it is: CVE-2017-3245 is a medium-severity vulnerability in Oracle FLEXCUBE Direct Banking, 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-2017-3245 in the wild and no public exploit code.

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

## Sources

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

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