Is CVE-2016-8308 exploited in the wild?

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

How severe is CVE-2016-8308?

Medium severity, with a CVSS score of 4.3, 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-8308?

A patch was published on 2017-01-17: Addressed in Oracle 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-8308 attacked?

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

Am I affected by CVE-2016-8308?

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-8308: Oracle FLEXCUBE Private Banking integrity vulnerability in Product Search

CVE-2016-8308 · Severity: medium · CVSS 4.3 · 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 unauthenticated attacker could trick a legitimate user into performing an action that allows the attacker to modify, add, or delete sensitive banking data. This could lead to unauthorized changes in financial records or instrument data, potentially impacting the integrity of banking operations.

Technologies: Oracle Flexcube Private Banking. Vendors: Oracle.

Quick answers

Is CVE-2016-8308 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2016-8308 being exploited in the wild.
How severe is CVE-2016-8308?: Medium severity, with a CVSS score of 4.3, 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-8308?: A patch was published on 2017-01-17: Addressed in Oracle 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-8308 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2016-8308?: 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

A vulnerability in the Product / Instrument Search subcomponent of Oracle FLEXCUBE Private Banking (versions 2.0.1, 2.2.0, and 12.0.1) allows an unauthenticated attacker with network access via HTTP to compromise the system. The exploit requires human interaction from a person other than the attacker, suggesting a UI-based attack such as Cross-Site Request Forgery (CSRF) or a similar client-side injection. Successful exploitation can result in unauthorized update, insert, or delete access to a subset of FLEXCUBE Private Banking data. The vulnerability has a CVSS v3.0 base score of 4.3, primarily impacting data integrity. Oracle addressed this 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 NVD publication
2017-01-17: patched: Addressed in Oracle January 2017 Critical Patch Update

References

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