Is CVE-2016-8301 exploited in the wild?

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

How severe is CVE-2016-8301?

Medium severity, with a CVSS score of 4.3, published 27 January 2017.

Which products and versions are affected?

Oracle Flexcube Universal Banking 11.3.0, 11.4.0, 12.0.1, 12.0.2, 12.0.3, 12.1.0, 12.2.0.

Is there a fix for CVE-2016-8301?

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-8301 attacked?

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

Am I affected by CVE-2016-8301?

Check whether you run Oracle Flexcube Universal 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-8301: Oracle FLEXCUBE Universal Banking integrity vulnerability in Core

CVE-2016-8301 · Severity: medium · CVSS 4.3 · Published 2017-01-27

Oracle FLEXCUBE Universal Banking, a core banking platform used for managing financial transactions and customer data, contains a security vulnerability in its Core subcomponent. An unauthenticated attacker could trick a legitimate user into performing an action that allows the attacker to modify, insert, or delete certain banking data. While the attacker cannot view sensitive information, this could lead to unauthorized changes in financial records or system configurations.

Technologies: Oracle Flexcube Universal Banking. Vendors: Oracle.

Quick answers

Is CVE-2016-8301 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2016-8301 being exploited in the wild.
How severe is CVE-2016-8301?: Medium severity, with a CVSS score of 4.3, published 27 January 2017.
Which products and versions are affected?: Oracle Flexcube Universal Banking 11.3.0, 11.4.0, 12.0.1, 12.0.2, 12.0.3, 12.1.0, 12.2.0.
Is there a fix for CVE-2016-8301?: 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-8301 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2016-8301?: Check whether you run Oracle Flexcube Universal 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

This vulnerability exists in the Core subcomponent of Oracle FLEXCUBE Universal Banking. It is classified as an 'easily exploitable' flaw that allows an unauthenticated attacker with network access via HTTP to impact the integrity of the system. The exploit requires human interaction from a person other than the attacker (typically a legitimate user), suggesting a vulnerability class such as Cross-Site Request Forgery (CSRF) or a similar UI-based attack. Successful exploitation can result in unauthorized update, insert, or delete access to a subset of FLEXCUBE Universal Banking data. Oracle addressed this in the January 2017 Critical Patch Update.

Affected products

Oracle FLEXCUBE Universal Banking 11.3.0, 11.4.0, 12.0.1, 12.0.2, 12.0.3, 12.1.0, 12.2.0

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.