# CVE-2017-3475: Denial of service in FLEXCUBE Private Banking

> A low-privileged attacker can cause a partial denial of service in Oracle FLEXCUBE Private Banking via network access.

- **Severity:** Medium 5.0 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:L`)
- **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:** 24 Apr 2017
- **Updated:** 7 Oct 2024
- **Also known as:** GHSA-rf6g-5h3g-x923

## What is CVE-2017-3475?

CVE-2017-3475 is a medium-severity denial of service vulnerability in Oracle Flexcube Private Banking, published on 24 Apr 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Vulnerability in the Oracle FLEXCUBE Private Banking component of Oracle Financial Services Applications (subcomponent: Miscellaneous). Supported versions that are affected are 2.0.0, 2.0.1, 2.2.0.1 and 12.0.1. Easily "exploitable" vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle FLEXCUBE Private Banking. While the vulnerability is in Oracle FLEXCUBE Private Banking, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS) of Oracle FLEXCUBE Private Banking. CVSS 3.0 Base Score 5.0 (Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:L).

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

It affects 1 product.


Products: Oracle Flexcube Private Banking.

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

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

## Is CVE-2017-3475 being exploited?

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

## Other vulnerabilities in Oracle Flexcube Private Banking

- [CVE-2016-8312](https://insights.sbomify.com/CVE-2016-8312/): Missing authorization in FLEXCUBE Private Banking (high 8.2)
- [CVE-2017-3472](https://insights.sbomify.com/CVE-2017-3472/): Missing authorization in FLEXCUBE Private Banking (high 8.1)
- [CVE-2016-8298](https://insights.sbomify.com/CVE-2016-8298/): Missing authorization in FLEXCUBE Private Banking 2.0.1;2.2.0;12.0.1 (high 8.1)
- [CVE-2017-3476](https://insights.sbomify.com/CVE-2017-3476/): Missing authorization in FLEXCUBE Private Banking (high 7.1)
- [CVE-2017-10006](https://insights.sbomify.com/CVE-2017-10006/): Missing authorization in FLEXCUBE Private Banking (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-3475 is a medium-severity denial of service vulnerability in Oracle Flexcube Private Banking, published on 24 Apr 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-3475 in the wild and no public exploit code.

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

## Sources

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

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