# CVE-2017-10181: Denial of service in FLEXCUBE Direct Banking

> Low-privileged attackers can cause a complete denial of service and unauthorized data access in Oracle FLEXCUBE Direct Banking via the Forgot Password feature.

- **Severity:** Medium 6.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Aug 2017
- **Updated:** 4 Oct 2024
- **Also known as:** GHSA-8w8c-v4pq-fm9h

## What is CVE-2017-10181?

CVE-2017-10181 is a medium-severity denial of service vulnerability in Oracle Corporation FLEXCUBE Direct Banking, published on 8 Aug 2017. Any signed-in user can exploit it over the network, 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: Forgot Password). Supported versions that are affected are 12.0.2 and 12.0.3. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle FLEXCUBE Direct Banking. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle FLEXCUBE Direct Banking as well as unauthorized update, insert or delete access to some of Oracle FLEXCUBE Direct Banking accessible data and unauthorized read access to a subset of Oracle FLEXCUBE Direct Banking accessible data. CVSS 3.0 Base Score 6.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:H).

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

It affects 1 product.


Products: Oracle Flexcube Direct Banking.

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

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

## Is CVE-2017-10181 being exploited?

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

## Other vulnerabilities in Oracle Corporation FLEXCUBE Direct Banking

- [CVE-2016-0699](https://insights.sbomify.com/CVE-2016-0699/): Other in n/a (critical 9.1)
- [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)
- [CVE-2019-2549](https://insights.sbomify.com/CVE-2019-2549/): Cross-site scripting in FLEXCUBE Direct Banking (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-10181 is a medium-severity denial of service vulnerability in Oracle Corporation FLEXCUBE Direct Banking, published on 8 Aug 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-10181 in the wild and no public exploit code.

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

## Sources

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

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