Is CVE-2016-8298 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2016-8298 being exploited in the wild.

How severe is CVE-2016-8298?

High severity, with a CVSS score of 8.1, published 27 January 2017.

Which products and versions are affected?

Oracle Flexcube Private Banking 2.0.1, 2.2.0, 12.0.1.

Is there a fix for CVE-2016-8298?

A patch was published on 2017-01-27: Fix released in January 2017 Critical Patch Update Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2016-8298 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2016-8298?

Check whether you run Oracle Flexcube Private Banking at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2016-8298: Oracle FLEXCUBE Private Banking improper access control in Product Search

CVE-2016-8298 · Severity: high · CVSS 8.1 · Published 2017-01-27

A vulnerability exists in Oracle FLEXCUBE Private Banking, a platform used by financial institutions to manage wealth and investment services. An attacker with basic user access can exploit this flaw to view, modify, or delete sensitive banking data. This could lead to unauthorized financial transactions, loss of customer data integrity, and significant regulatory or reputational damage.

Technologies: Oracle Flexcube Private Banking. Vendors: Oracle.

Quick answers

Is CVE-2016-8298 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2016-8298 being exploited in the wild.
How severe is CVE-2016-8298?: High severity, with a CVSS score of 8.1, published 27 January 2017.
Which products and versions are affected?: Oracle Flexcube Private Banking 2.0.1, 2.2.0, 12.0.1.
Is there a fix for CVE-2016-8298?: A patch was published on 2017-01-27: Fix released in January 2017 Critical Patch Update Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2016-8298 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2016-8298?: Check whether you run Oracle Flexcube Private Banking at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

An improper access control vulnerability (CWE-284) exists in the Product / Instrument Search subcomponent of Oracle FLEXCUBE Private Banking. The flaw is easily exploitable by a low-privileged attacker with network access via HTTP. Successful exploitation allows the attacker to gain unauthorized read, create, delete, or modification access to critical data or all accessible data within the application. The vulnerability affects versions 2.0.1, 2.2.0, and 12.0.1. Oracle addressed this issue in the January 2017 Critical Patch Update.

Affected products

Oracle FLEXCUBE Private Banking 2.0.1, 2.2.0, 12.0.1

Timeline

2017-01-27: advisory: Initial disclosure by Oracle
2017-01-27: patched: Fix released in January 2017 Critical Patch Update

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.